Triple
T4232695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bison bison |
E94616
|
entity |
| Predicate | hasBodyLength |
P31708
|
FINISHED |
| Object | approximately 2 to 3.5 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 2 to 3.5 meters | Statement: [Bison bison, hasBodyLength, approximately 2 to 3.5 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBodyLength Context triple: [Bison bison, hasBodyLength, approximately 2 to 3.5 meters]
-
A.
hasBodyLengthRange
chosen
Indicates the range of possible body lengths associated with an entity, typically expressed as a minimum and maximum value.
-
B.
hasBodyOf
Indicates that one entity possesses, contains, or is composed of the physical body or main substance of another entity.
-
C.
hasInternalBody
Indicates that one entity possesses an internal body or internal bodily structure relative to another entity or context.
-
D.
maximumBodyLength
Indicates that there is an upper limit on the allowable length or size of a body (e.g., content, message, or object) in this relationship or action.
-
E.
hasSupportBody
Indicates that one entity serves as a supporting structure or body for another entity.
- 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_69b34537cc6481909cd0a96acbb33ef7 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e65720c819087c4022c774ff7c3 |
completed | March 12, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69b347f3bd188190b0cd613e8a5c1683 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:05 p.m.