Triple
T7528299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mont Orohena |
E177951
|
entity |
| Predicate | isExtinctOrDormant |
P65652
|
FINISHED |
| Object | dormant |
—
|
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: dormant | Statement: [Mont Orohena, isExtinctOrDormant, dormant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isExtinctOrDormant Context triple: [Mont Orohena, isExtinctOrDormant, dormant]
-
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.
hasExtinctMembers
Indicates that at least some members of the referenced group, class, or category are no longer living or existing.
-
C.
hasExtinctSpecies
Indicates that at least one species associated with the subject entity is no longer extant (i.e., has gone extinct).
-
D.
possiblyExtinctBy
Indicates that an entity is believed or suspected to have gone extinct as a result of the specified cause or agent.
-
E.
extantStatus
chosen
Indicates the current existence state of an entity, such as whether it is still present, active, or has ceased to exist.
- 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_69c69f29bf3081909a146aec7755f185 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f81e19208190965f211d057f7fdf |
completed | March 27, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d6bb808190bdd04499fd3bceb6 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:47 p.m.