Triple
T12496165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Near Threatened |
E298689
|
entity |
| Predicate | isNonThreatenedCategory |
P105299
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Near Threatened, isNonThreatenedCategory, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNonThreatenedCategory Context triple: [Near Threatened, isNonThreatenedCategory, true]
-
A.
threatenedBy
Indicates that one entity poses a danger or potential harm to another entity.
-
B.
hasConservationConcernIn
Indicates that an entity is subject to a specified conservation concern status within a particular geographic area or jurisdiction.
-
C.
isNonGameBird
Indicates that the subject is classified as a bird that is not hunted or managed as game.
-
D.
conservationStatus
Indicates the level of risk or protection category assigned to an entity, typically reflecting how threatened it is with extinction or decline.
-
E.
areEndangeredOrVulnerable
Indicates that the entities are classified as being at risk of extinction, either endangered or vulnerable, according to conservation status criteria.
- F. None of above. chosen
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_69d6ada4cd388190ae3bbf83ff87057a |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94e8a706c8190873623eab7db607d |
completed | April 10, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69d94d41f3cc8190a3331fb9a895306f |
completed | April 10, 2026, 7:19 p.m. |
| PDg | Predicate description generation | batch_69d94e87e0e88190bc49dcfe4954c7e0 |
completed | April 10, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:57 p.m.