Triple
T9149946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pomerape Volcano |
E219558
|
entity |
| Predicate | isDormantOrExtinct |
P17096
|
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: [Pomerape Volcano, isDormantOrExtinct, dormant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDormantOrExtinct Context triple: [Pomerape Volcano, isDormantOrExtinct, dormant]
-
A.
hasExtinctMembers
Indicates that at least some members of the referenced group, class, or category are no longer living or existing.
-
B.
isDormant
chosen
Indicates that an entity is currently inactive or in a resting state, with its usual functions or activities temporarily suspended.
-
C.
hasExtinctSpecies
Indicates that at least one species associated with the subject entity is no longer extant (i.e., has gone extinct).
-
D.
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.
-
E.
extantStatus
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_69ca83e121dc81909912bd66953081c5 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca96908d88190a1d12517f6d1aece |
completed | April 1, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69cc6603ce8c8190bf6e8d6754bdec54 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:20 p.m.