Triple
T30693820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laysan rail |
E781401
|
entity |
| Predicate | extinctionSignificance |
P170485
|
FINISHED |
| Object | example of island rail extinction |
—
|
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: example of island rail extinction | Statement: [Laysan rail, extinctionSignificance, example of island rail extinction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extinctionSignificance Context triple: [Laysan rail, extinctionSignificance, example of island rail extinction]
-
A.
impactOfExtinction
Indicates the consequences or effects that the extinction of an entity has on other entities, systems, or conditions.
-
B.
massExtinctionImpact
Indicates a large-scale, catastrophic event or process that causes widespread and rapid extinction across many species or lineages.
-
C.
massExtinctionConsequence
Indicates that an event or factor results in, contributes to, or is a direct outcome of a mass extinction event.
-
D.
extinctionType
Indicates the specific manner or category by which an entity ceases to exist or becomes extinct.
-
E.
extinctionSymbolism
Indicates a symbolic association between something and the concept, threat, or process of extinction.
- 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_69f224ab24e08190991d6edb6df58e8b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f69063edbc81909e7735954aabee0b |
completed | May 3, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68f6584a88190a8c4d95c0c84bee9 |
completed | May 2, 2026, 11:57 p.m. |
Created at: April 29, 2026, 8:33 p.m.