Triple
T4232694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bison bison |
E94616
|
entity |
| Predicate | hasBodyMass |
P26037
|
FINISHED |
| Object | up to about 1000 kg in large males |
—
|
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: up to about 1000 kg in large males | Statement: [Bison bison, hasBodyMass, up to about 1000 kg in large males]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBodyMass Context triple: [Bison bison, hasBodyMass, up to about 1000 kg in large males]
-
A.
hasMass_kg
chosen
Indicates that an entity possesses a specific mass measured in kilograms.
-
B.
residesOverBodyType
Indicates that one entity is positioned or located above another entity that is characterized by a specific body type.
-
C.
parentBodyType
Indicates that one entity has a body type that serves as the parent or base classification from which another entity's body type is derived or organized.
-
D.
hasBodyOf
Indicates that one entity possesses, contains, or is composed of the physical body or main substance of another entity.
-
E.
primaryBodyType
Indicates the main physical form or category that characterizes an entity’s overall body structure or composition.
- 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.