Triple
T9706395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lemuriformes |
E234908
|
entity |
| Predicate | locomotionIncludes |
P14493
|
FINISHED |
| Object | vertical clinging and leaping in some families |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: vertical clinging and leaping in some families | Statement: [Lemuriformes, locomotionIncludes, vertical clinging and leaping in some families]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locomotionIncludes Context triple: [Lemuriformes, locomotionIncludes, vertical clinging and leaping in some families]
-
A.
locomotion
Indicates movement or the ability to move from one place to another.
-
B.
usesStructureForLocomotion
Indicates that an entity moves or travels by employing a particular physical structure or body part as its means of locomotion.
-
C.
hasLocomotive
Indicates that one entity possesses or is equipped with a locomotive as part of its composition or operation.
-
D.
pursuitLocomotive
Indicates engaging in locomotion specifically aimed at following or chasing another entity.
-
E.
movementCharacteristic
chosen
Indicates how an entity moves or behaves in motion, such as its style, pattern, or quality of movement.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ca84cc78808190a56f3402b7c139a7 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9da4c53c81908ba4bfe4d9ca8814 |
completed | April 1, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69cd03b641408190942464eaf174c6b5 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:19 p.m.