Triple
T26813207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sivapithecus |
E672052
|
entity |
| Predicate | cranialMorphology |
P117695
|
FINISHED |
| Object | narrow interorbital distance |
—
|
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: narrow interorbital distance | Statement: [Sivapithecus, cranialMorphology, narrow interorbital distance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cranialMorphology Context triple: [Sivapithecus, cranialMorphology, narrow interorbital distance]
-
A.
skullMorphology
chosen
Indicates a relationship where entities are characterized or compared based on the form, structure, or anatomical features of their skulls.
-
B.
cranialStructureFunction
Indicates that a relationship exists between a cranial structure and the specific function or role it performs.
-
C.
majorCranialComponent
Indicates that one anatomical structure constitutes a principal or primary component of another structure within the cranium.
-
D.
cranialCapacity
Indicates the volume or size of the interior space of the skull that can house the brain.
-
E.
cranialCapacityRelativeToModernHumans
Indicates how an entity’s cranial capacity compares in size to that of modern humans.
- 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_69eeb3225a3c8190aaf6746efeded2f3 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6247480cc8190a887eedaeb94615c |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f623a7539c8190b71797f583da9f63 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 4:30 a.m.