Triple
T25294271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | little bustard |
E634171
|
entity |
| Predicate | hasScientificNameAbbreviation |
P85126
|
FINISHED |
| Object | T. tetrax |
E1672867
|
NE 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: T. tetrax | Statement: [little bustard, hasScientificNameAbbreviation, T. tetrax]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScientificNameAbbreviation Context triple: [little bustard, hasScientificNameAbbreviation, T. tetrax]
-
A.
scientificNameAbbreviation
chosen
Indicates that one entity is an abbreviated or shortened form of the scientific name of another entity.
-
B.
taxonAbbreviation
Indicates that one taxonomic entity is associated with a standardized abbreviated form of its scientific name.
-
C.
hasNameAbbreviation
Indicates that an entity is associated with a shortened or abbreviated form of its full name.
-
D.
hasScientificDesignation
Indicates that an entity is associated with a specific formal scientific name or designation used in scientific classification or nomenclature.
-
E.
hasAbbreviationStatus
Indicates that an entity has a particular status or condition regarding its abbreviation (e.g., whether it is abbreviated, how, or to what extent).
- F. None of above.
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_69e75a9503d48190b80a005c6af0cb50 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f606c79ad081908369605f72e65ca6 |
completed | May 2, 2026, 2:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a1075db359c819092ac3b1c01378fc4 |
completed | May 22, 2026, 3:27 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 21, 2026, 1:22 p.m.