Triple
T1741813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Axis axis |
E38248
|
entity |
| Predicate | iucnStatus |
P1339
|
FINISHED |
| Object | Least Concern |
—
|
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: Least Concern | Statement: [Axis axis, iucnStatus, Least Concern]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: iucnStatus Context triple: [Axis axis, iucnStatus, Least Concern]
-
A.
conservationStatus
chosen
Indicates the level of risk or protection category assigned to an entity, typically reflecting how threatened it is with extinction or decline.
-
B.
IUCNStatusSystem
Indicates the conservation status classification framework used to assign an IUCN threat category to a species or taxon.
-
C.
areEndangeredIn
Indicates that the entities are classified as endangered within a specified geographic area or jurisdiction.
-
D.
ecologicalStatus
Indicates the condition or health of an ecosystem or environment, often in terms of its quality, integrity, or degree of disturbance.
-
E.
isFunctionallyExtinctInTheWild
Indicates that the species no longer performs its ecological role in the wild because its population is too small, fragmented, or non-viable, even if some individuals still exist.
- 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_69a8862b01a48190ab47209063af82d9 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab3c2559ac8190905186406fcaccb9 |
completed | March 6, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69aa61c4023c819099cbe439aefda71f |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.