Triple
T27347981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homo habilis |
E684279
|
entity |
| Predicate | estimatedStature |
P38193
|
FINISHED |
| Object | approximately 1.0–1.4 meters |
—
|
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: approximately 1.0–1.4 meters | Statement: [Homo habilis, estimatedStature, approximately 1.0–1.4 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estimatedStature Context triple: [Homo habilis, estimatedStature, approximately 1.0–1.4 meters]
-
A.
estimatedHeadHeightInMeters
Indicates the estimated vertical height of a person's head, measured in meters.
-
B.
heightEstimate
chosen
Indicates an estimated or approximate value for the height of an entity, rather than a precisely measured height.
-
C.
estimatedHeightAtHipsInMeters
Indicates the estimated vertical height, measured in meters, of an entity at the level of its hips.
-
D.
heightDescription
Indicates how tall an entity is, typically expressed in descriptive or qualitative terms rather than a precise measurement.
-
E.
averageStatureCharacteristic
Indicates that an entity has a stature (height or overall size) that is typical or average relative to a relevant comparison group.
- 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_69ef1480a76481908684256ddd5bfda3 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 27, 2026, 11:46 a.m.