Triple
T15786338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turkana Boy |
E382746
|
entity |
| Predicate | faceMorphology |
P31336
|
FINISHED |
| Object | prognathic face |
—
|
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: prognathic face | Statement: [Turkana Boy, faceMorphology, prognathic face]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: faceMorphology Context triple: [Turkana Boy, faceMorphology, prognathic face]
-
A.
faceValueType
Indicates the type or category of a financial instrument’s face (nominal) value, such as how that value is defined or represented.
-
B.
facesChallenge
Indicates that an entity is confronted with a difficulty, obstacle, or demanding situation that must be dealt with or overcome.
-
C.
facehuggerFunction
Indicates a parasitic interaction where one entity attaches to another’s face to implant or initiate a harmful internal process.
-
D.
faceType
chosen
Indicates the specific shape or structural category of a face that an entity possesses or is characterized by.
-
E.
faceliftFeature
Indicates that one entity is a specific feature, component, or aspect involved in a facelift procedure or facelift-related modification of the other entity.
- 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_69d86da16e188190b89af699f1ed0bfe |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0540380448190a025338f0e62e6d1 |
completed | April 16, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69e00537bd1c81908d6e832792fd934f |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:48 a.m.