Triple
T25283820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | great bustard |
E633883
|
entity |
| Predicate | maleLengthRange |
P37841
|
FINISHED |
| Object | 90–105 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: 90–105 cm | Statement: [great bustard, maleLengthRange, 90–105 cm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maleLengthRange Context triple: [great bustard, maleLengthRange, 90–105 cm]
-
A.
maleLength
chosen
Indicates that the relationship specifies the length or size measurement of a male individual or male part of an entity.
-
B.
hornLengthMale
Indicates the measured length of the horns specifically for male individuals in the relationship.
-
C.
averageHeadBodyLengthRangeMale
Indicates the range of average head-to-body lengths observed specifically in male individuals of a species.
-
D.
tailLengthMale
Indicates the length of the tail specifically for male individuals in the context of the described relationship or measurement.
-
E.
averageBodyLengthMale
Indicates the typical or mean body length measured specifically for male individuals of a species 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_69e75a9402fc81909362ca85277c06d9 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48e0718908190a2ebc862db79e2ea |
completed | May 1, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 1:19 p.m.