Triple
T27079378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homo naledi |
E685550
|
entity |
| Predicate | ribcageMorphology |
P161826
|
FINISHED |
| Object | more conical, similar to australopiths |
—
|
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 conical, similar to australopiths | Statement: [Homo naledi, ribcageMorphology, more conical, similar to australopiths]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ribcageMorphology Context triple: [Homo naledi, ribcageMorphology, more conical, similar to australopiths]
-
A.
limbMorphology
Indicates the structural form, shape, and configuration of an organism’s limbs in relation to its body.
-
B.
skullMorphology
Indicates a relationship where entities are characterized or compared based on the form, structure, or anatomical features of their skulls.
-
C.
hasRibs
Indicates that one entity possesses ribs as anatomical structures.
-
D.
anatomicalFeature
Indicates that one entity is an anatomical part, structure, or feature of another entity.
-
E.
pelvisMorphology
Indicates the structural characteristics or shape-related features of a pelvis in relation to another entity or condition.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69f61fa35ac48190890102c348ed81a0 |
completed | May 2, 2026, 4 p.m. |
Created at: April 27, 2026, 8:33 a.m.