Triple
T27314141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sahelanthropus |
E689292
|
entity |
| Predicate | estimatedBrainVolume |
P66567
|
FINISHED |
| Object | about 320 to 380 cubic centimeters |
—
|
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: about 320 to 380 cubic centimeters | Statement: [Sahelanthropus, estimatedBrainVolume, about 320 to 380 cubic centimeters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estimatedBrainVolume Context triple: [Sahelanthropus, estimatedBrainVolume, about 320 to 380 cubic centimeters]
-
A.
cranialCapacity
chosen
Indicates the volume or size of the interior space of the skull that can house the brain.
-
B.
hasBrainToBodyRatio
Indicates the proportional relationship between the size or mass of an entity’s brain and the size or mass of its body.
-
C.
brainMass
Indicates the mass of an entity’s brain, typically measured as a physical quantity such as in grams or kilograms.
-
D.
cranialCapacityRelativeToApes
Indicates that the cranial capacity of one entity is being compared in size or proportion to that typically found in apes.
-
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_69ef355c53a08190a8a92e355a7ce115 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 27, 2026, 11:29 a.m.