Triple
T26713262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oreopithecus |
E673478
|
entity |
| Predicate | footMorphologySuggests |
P161154
|
FINISHED |
| Object | limited efficient terrestrial bipedalism |
—
|
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: limited efficient terrestrial bipedalism | Statement: [Oreopithecus, footMorphologySuggests, limited efficient terrestrial bipedalism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: footMorphologySuggests Context triple: [Oreopithecus, footMorphologySuggests, limited efficient terrestrial bipedalism]
-
A.
footMorphologySuggests
chosen
Indicates that the structure or shape of a foot provides evidence or clues pointing toward a particular characteristic, behavior, or classification.
-
B.
footType
Indicates the specific kind or classification of feet that an entity possesses or is characterized by.
-
C.
toeShape
Indicates the specific form or contour of an entity’s toe or toe area.
-
D.
legCharacteristic
Indicates a characteristic, property, or attribute that specifically pertains to the legs of an entity.
-
E.
hasHeelType
Indicates that an item (typically footwear) possesses a specific type or style of heel.
- 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_69eecda3a22881908f3061c760b9d542 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f61a17a7788190946f7e32d63cd43f |
completed | May 2, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69f611ab768c8190b1849c15a3e59dda |
completed | May 2, 2026, 3 p.m. |
Created at: April 27, 2026, 3:36 a.m.