Triple
T24122525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paranthropus aethiopicus |
E597700
|
entity |
| Predicate | dentalAdaptation |
P128829
|
FINISHED |
| Object | massive jaws |
—
|
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: massive jaws | Statement: [Paranthropus aethiopicus, dentalAdaptation, massive jaws]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dentalAdaptation Context triple: [Paranthropus aethiopicus, dentalAdaptation, massive jaws]
-
A.
toothAdaptation
chosen
Indicates how an organism’s teeth are structurally or functionally modified in response to its diet, environment, or evolutionary pressures.
-
B.
dentition
Indicates the type, arrangement, or condition of teeth that an entity possesses.
-
C.
distinguishingDentalFeature
Indicates that one entity has a dental characteristic that serves to differentiate it from another entity or group.
-
D.
toothReplacement
Indicates a relationship where one tooth is substituted or restored by another tooth or dental prosthetic, replacing its function or position.
-
E.
tongueAdaptation
Indicates how an entity’s tongue is structurally or functionally modified to perform specific tasks or suit particular environmental or behavioral demands.
- 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_69e288c74200819098ab875b592cb39f |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dee5937c819092396751c23553ca |
completed | April 29, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:05 p.m.