Triple
T1778573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aquila adalberti |
E39235
|
entity |
| Predicate | formerTaxonomicStatus |
P10572
|
FINISHED |
| Object | subspecies of Aquila heliaca |
—
|
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: subspecies of Aquila heliaca | Statement: [Aquila adalberti, formerTaxonomicStatus, subspecies of Aquila heliaca]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerTaxonomicStatus Context triple: [Aquila adalberti, formerTaxonomicStatus, subspecies of Aquila heliaca]
-
A.
taxonomicStatus
chosen
Indicates the formal classification status of a taxon within a taxonomic system, such as whether it is accepted, synonymized, provisional, or invalid.
-
B.
formerDesignation
Indicates that an entity previously held a particular title, role, or designation that it no longer holds.
-
C.
formerAdministrativeStatus
Indicates that an entity previously held, but no longer holds, a particular administrative status or role.
-
D.
formerCategory
Indicates that an entity previously belonged to a given category but no longer does.
-
E.
formerState
Indicates that an entity previously held the status or condition of a particular state but no longer does so.
- 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_69a88630519c8190a17addd83c4a3ef4 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab74dc9d1481908084ef07872a71f8 |
completed | March 7, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69aa61cf3ca881908641fd73ce2f7c9d |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.