Triple
T25500930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ursus arctos |
E639107
|
entity |
| Predicate | averageMaleMassRange |
P49195
|
FINISHED |
| Object | 135–390 kg |
—
|
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: 135–390 kg | Statement: [Ursus arctos, averageMaleMassRange, 135–390 kg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: averageMaleMassRange Context triple: [Ursus arctos, averageMaleMassRange, 135–390 kg]
-
A.
maleBodyMass
chosen
Indicates that the relationship specifies the body mass or weight associated with a male individual.
-
B.
averageHeadBodyLengthRangeMale
Indicates the range of average head-to-body lengths observed specifically in male individuals of a species.
-
C.
averageMaleHeight
Indicates the typical or mean height value associated with male individuals in a given population or context.
-
D.
averageBodyLengthMale
Indicates the typical or mean body length measured specifically for male individuals of a species or group.
-
E.
averageHeightRange
Indicates the typical minimum and maximum height values that characterize the usual height span associated with an entity or group.
- 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_69e75dbbd2a88190b70e1e645de14b9a |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f801e8f8819093ca7a9eb910fd33 |
completed | May 2, 2026, 1:11 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 2:42 p.m.