Triple
T14999413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mitu mitu |
E374043
|
entity |
| Predicate | extinctInTheWild |
P50779
|
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: [Mitu mitu, extinctInTheWild, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extinctInTheWild Context triple: [Mitu mitu, extinctInTheWild, true]
-
A.
enemyTypeInExtinction
Indicates that a particular enemy belongs to a category or type that is present in an extinction-related context (e.g., an extinction mode, event, or scenario).
-
B.
wasExtinctInTheWild
chosen
Indicates that an entity no longer existed in natural habitats during a specified time, surviving only in captivity or controlled environments.
-
C.
thoughtExtinct
Indicates that something was previously believed to no longer exist or to have died out, but is now recognized or suggested to still exist.
-
D.
extinct
Indicates that the referenced entity no longer exists as a living or active member of its former kind or category.
-
E.
hasExtinctSpecies
Indicates that at least one species associated with the subject entity is no longer extant (i.e., has gone extinct).
- 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded71a5618819083ae96a79735ef98 |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a6531a88190acde65199a477350 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:54 a.m.