Triple
T27348011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homo floresiensis |
E684280
|
entity |
| Predicate | averageHeightCentimetres |
P37840
|
FINISHED |
| Object | about 106 |
—
|
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 106 | Statement: [Homo floresiensis, averageHeightCentimetres, about 106]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: averageHeightCentimetres Context triple: [Homo floresiensis, averageHeightCentimetres, about 106]
-
A.
averageHeight
chosen
Indicates that the relationship specifies the mean height value calculated from a set of entities or measurements.
-
B.
averageHeightRange
Indicates the typical minimum and maximum height values that characterize the usual height span associated with an entity or group.
-
C.
averageStatureCharacteristic
Indicates that an entity has a stature (height or overall size) that is typical or average relative to a relevant comparison group.
-
D.
averageMaleHeight
Indicates the typical or mean height value associated with male individuals in a given population or context.
-
E.
averageFemaleHeight
Indicates the typical or mean height value observed among female individuals in a given group or population.
- 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_69f65876c52c8190bc889c7a67bd07f3 |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 27, 2026, 11:46 a.m.