Triple
T16753307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hippotragus |
E407140
|
entity |
| Predicate | hasHeadBodyLength |
P31708
|
FINISHED |
| Object | approximately 190–240 cm |
—
|
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 190–240 cm | Statement: [Hippotragus, hasHeadBodyLength, approximately 190–240 cm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeadBodyLength Context triple: [Hippotragus, hasHeadBodyLength, approximately 190–240 cm]
-
A.
hasBodyLengthRange
chosen
Indicates the range of possible body lengths associated with an entity, typically expressed as a minimum and maximum value.
-
B.
hasHeadCount
Indicates that an entity is associated with a specific number of individuals, typically representing the size or count of people (or similar units) related to it.
-
C.
hasBodyOf
Indicates that one entity possesses, contains, or is composed of the physical body or main substance of another entity.
-
D.
hasTopBody
Indicates that one entity possesses or is characterized by a primary upper body section.
-
E.
hasCanonicalNumberOfHeads
Indicates that an entity possesses the standard or officially recognized number of heads for its kind.
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3aa28fd3c8190972e2e69ea7dece0 |
completed | April 18, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69e319cbd79c8190a03587a61c18bec0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.