Triple
T3758787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arabian oryx |
E82111
|
entity |
| Predicate | wasExtinctInTheWild |
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: [Arabian oryx, wasExtinctInTheWild, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasExtinctInTheWild Context triple: [Arabian oryx, wasExtinctInTheWild, true]
-
A.
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.
-
B.
wasOnceNearExtinction
Indicates that the entity’s population or existence was at one time so low or threatened that it was in serious danger of disappearing entirely.
-
C.
extinctionDate
Indicates the date or time at which an entity (typically a species or lineage) ceased to exist.
-
D.
hasExtinctSpecies
Indicates that at least one species associated with the subject entity is no longer extant (i.e., has gone extinct).
-
E.
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.
- 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_69ad8b1db40081908b61ffa6b78afd4d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcbc20b20819095fedf803aadc53a |
completed | March 8, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69adc04c851c8190ae5eaebf36df539b |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc0fe3e3c8190bd886c7745c172a0 |
completed | March 8, 2026, 6:33 p.m. |
Created at: March 8, 2026, 3:35 p.m.