Triple
T9286931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catagonus wagneri |
E223416
|
entity |
| Predicate | thoughtStatusBeforeRediscovery |
P87406
|
FINISHED |
| Object | extinct in the wild |
—
|
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: extinct in the wild | Statement: [Catagonus wagneri, thoughtStatusBeforeRediscovery, extinct in the wild]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thoughtStatusBeforeRediscovery Context triple: [Catagonus wagneri, thoughtStatusBeforeRediscovery, extinct in the wild]
-
A.
discoveredBefore
Indicates that one entity was discovered earlier in time than another entity.
-
B.
rediscoveredAt
Indicates that an entity was found or identified again at a particular time or place after having been lost, forgotten, or unknown.
-
C.
previouslyObserved
Indicates that the subject entity has been seen, recorded, or encountered at some earlier time prior to the current context.
-
D.
revealedBefore
Indicates that one entity becomes known, disclosed, or made apparent earlier in time than another entity.
-
E.
discoveredSince
Indicates that one entity has been discovered starting from, or at some point after, a specified time or event associated with another entity.
- 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_69ca8422ddf881908a3f8f876c9f53aa |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd0821b1108190b16e9570b09a14de |
completed | April 1, 2026, 11:57 a.m. |
| PD | Predicate disambiguation | batch_69cc7a576ec88190bbb787eb82e2e539 |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc94b796788190816b71b1e9996288 |
completed | April 1, 2026, 3:44 a.m. |
Created at: March 30, 2026, 7:35 p.m.