Triple
T31978847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mission blue butterfly |
E816521
|
entity |
| Predicate | listedAsEndangered |
P1339
|
FINISHED |
| Object | 1976 |
—
|
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: 1976 | Statement: [Mission blue butterfly, listedAsEndangered, 1976]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: listedAsEndangered Context triple: [Mission blue butterfly, listedAsEndangered, 1976]
-
A.
areEndangeredIn
Indicates that the entities are classified as endangered within a specified geographic area or jurisdiction.
-
B.
areEndangeredOrVulnerable
Indicates that the entities are classified as being at risk of extinction, either endangered or vulnerable, according to conservation status criteria.
-
C.
isEndangeredDueTo
Indicates that an entity is endangered as a result of the specific cause or factor represented by the related entity.
-
D.
areEndangeredInPart
Indicates that an entity is endangered only in certain regions or parts of its overall range, rather than throughout its entire distribution.
-
E.
conservationStatus
chosen
Indicates the level of risk or protection category assigned to an entity, typically reflecting how threatened it is with extinction or decline.
- 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_69f348f6a3008190bfb59ca695fd68e2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b348d01c8190afa1fe9ece4de11a |
completed | May 3, 2026, 2:30 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:11 a.m.