Triple
T26831583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gigantopithecus |
E675512
|
entity |
| Predicate | teethMorphology |
P128829
|
FINISHED |
| Object | adapted for tough vegetation |
—
|
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: adapted for tough vegetation | Statement: [Gigantopithecus, teethMorphology, adapted for tough vegetation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teethMorphology Context triple: [Gigantopithecus, teethMorphology, adapted for tough vegetation]
-
A.
distinguishingDentalFeature
Indicates that one entity has a dental characteristic that serves to differentiate it from another entity or group.
-
B.
toothAdaptation
chosen
Indicates how an organism’s teeth are structurally or functionally modified in response to its diet, environment, or evolutionary pressures.
-
C.
dentition
Indicates the type, arrangement, or condition of teeth that an entity possesses.
-
D.
teethSownBy
Indicates that teeth were deliberately planted or scattered by a particular agent or source.
-
E.
typicalLocationOfTooth
Indicates the usual or characteristic anatomical location where a tooth is found or situated.
- 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_69eee9b776448190993a60b67fcc9545 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61fd623bc819091df736cf3419b99 |
completed | May 2, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 5:01 a.m.