Triple
T16731724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tibetan antelope |
E406606
|
entity |
| Predicate | hornLengthMale |
P124423
|
FINISHED |
| Object | about 50–60 centimetres |
—
|
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: about 50–60 centimetres | Statement: [Tibetan antelope, hornLengthMale, about 50–60 centimetres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hornLengthMale Context triple: [Tibetan antelope, hornLengthMale, about 50–60 centimetres]
-
A.
maleLength
Indicates that the relationship specifies the length or size measurement of a male individual or male part of an entity.
-
B.
tailLengthMale
Indicates the length of the tail specifically for male individuals in the context of the described relationship or measurement.
-
C.
averageHeadBodyLengthRangeMale
Indicates the range of average head-to-body lengths observed specifically in male individuals of a species.
-
D.
averageBodyLengthMale
Indicates the typical or mean body length measured specifically for male individuals of a species or group.
-
E.
averageMaleHornShape
Indicates the typical or most common horn shape observed in male individuals of a given group or species.
- F. None of above. chosen
Provenance (4 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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e39c362bb88190921fab43d76c3ee8 |
completed | April 18, 2026, 2:59 p.m. |
| PD | Predicate disambiguation | batch_69e319c807788190901250ab6e0ca55f |
completed | April 18, 2026, 5:42 a.m. |
| PDg | Predicate description generation | batch_69e326b9e84881909a9166e65bd850d6 |
completed | April 18, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:20 a.m.