Triple
T7057168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ursus thibetanus |
E164120
|
entity |
| Predicate | bodyLengthRange |
P31708
|
FINISHED |
| Object | 120–190 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: 120–190 cm | Statement: [Ursus thibetanus, bodyLengthRange, 120–190 cm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodyLengthRange Context triple: [Ursus thibetanus, bodyLengthRange, 120–190 cm]
-
A.
hasBodyLengthRange
chosen
Indicates the range of possible body lengths associated with an entity, typically expressed as a minimum and maximum value.
-
B.
bodySize
Indicates the relative physical magnitude or scale of an entity’s body, such as how large or small it is.
-
C.
hasLengthRange
Indicates that an entity’s length falls within a specified minimum-to-maximum range.
-
D.
memberOfBodySize
Indicates that one entity is a component or part whose size contributes to or characterizes the overall body size of another entity.
-
E.
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.
- 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_69c68861678881909961ddf4d779f750 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e4a3c36c819080942c59f1830ae8 |
completed | March 27, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bdc1f08190975fcdbbb1854d1e |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:38 p.m.