Triple
T27079377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homo naledi |
E685550
|
entity |
| Predicate | shoulderMorphology |
P26649
|
FINISHED |
| Object | more ape-like, oriented for climbing |
—
|
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: more ape-like, oriented for climbing | Statement: [Homo naledi, shoulderMorphology, more ape-like, oriented for climbing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shoulderMorphology Context triple: [Homo naledi, shoulderMorphology, more ape-like, oriented for climbing]
-
A.
limbMorphology
chosen
Indicates the structural form, shape, and configuration of an organism’s limbs in relation to its body.
-
B.
hasShoulderThatIsHighestPointOf
Indicates that an entity’s shoulder is the highest physical point or elevation on that entity.
-
C.
typicalShoulderLine
Indicates that one entity has a shoulder line that is characteristic or standard for the type, style, or category represented by the other entity.
-
D.
hasShoulderPatchShape
Indicates that one entity possesses a shoulder patch whose form or outline matches the specified shape.
-
E.
hasShoulderDiameter
Indicates the diameter measurement of an entity’s shoulder region or shoulder-related feature.
- 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_69ef14843b1481909d828b3d5a44550a |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f6231822ac8190887ebcb3b6d86d2b |
completed | May 2, 2026, 4:15 p.m. |
| PD | Predicate disambiguation | batch_69f61b40f02081909bd9c3ea73249163 |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 8:33 a.m.