Triple
T1778539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aquila adalberti |
E39235
|
entity |
| Predicate | IUCNRedListVersion |
P4569
|
FINISHED |
| Object | 3.1 |
—
|
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: 3.1 | Statement: [Aquila adalberti, IUCNRedListVersion, 3.1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IUCNRedListVersion Context triple: [Aquila adalberti, IUCNRedListVersion, 3.1]
-
A.
IUCNStatusSystem
chosen
Indicates the conservation status classification framework used to assign an IUCN threat category to a species or taxon.
-
B.
conservationStatus
Indicates the level of risk or protection category assigned to an entity, typically reflecting how threatened it is with extinction or decline.
-
C.
biodiversityStatus
Indicates the current condition or level of biological diversity associated with an entity, often in terms of richness, health, or conservation concern.
-
D.
areEndangeredIn
Indicates that the entities are classified as endangered within a specified geographic area or jurisdiction.
-
E.
taxonomicStatus
Indicates the formal classification status of a taxon within a taxonomic system, such as whether it is accepted, synonymized, provisional, or invalid.
- 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.