Triple
T27803331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Niuafoou |
E702305
|
entity |
| Predicate | hadEarlierEruption |
P22468
|
FINISHED |
| Object | 1886 eruption |
—
|
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: 1886 eruption | Statement: [Niuafoou, hadEarlierEruption, 1886 eruption]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadEarlierEruption Context triple: [Niuafoou, hadEarlierEruption, 1886 eruption]
-
A.
erupted
Indicates that a volcano or similar geological feature suddenly expelled lava, ash, gas, or other material in a violent outburst.
-
B.
hasEruptionEpisodes
Indicates that an entity (such as a volcano or geyser) undergoes one or more distinct eruption events over time.
-
C.
hasHistoryOf
Indicates that an entity has a documented prior occurrence or background of a specified condition, event, or state.
-
D.
hadEvent
chosen
Indicates that an entity experienced, hosted, or was associated with a specific event at some point in time.
-
E.
hasEruptionInCentury
Indicates that an eruption event occurred during a specified century.
- 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_69ef8408e0588190977cffa32dc33a29 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f63894e5848190aec428392562ab06 |
completed | May 2, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69f6370c8c7c8190a02ea82847bb6e76 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 5:36 p.m.