Triple
T5242673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Novarupta |
E118380
|
entity |
| Predicate | discoveredAsEruptionSource |
P59041
|
FINISHED |
| Object | 1950s |
—
|
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: 1950s | Statement: [Mount Novarupta, discoveredAsEruptionSource, 1950s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveredAsEruptionSource Context triple: [Mount Novarupta, discoveredAsEruptionSource, 1950s]
-
A.
notableEruption
Indicates that a volcano or geothermal feature has experienced an eruption considered historically or scientifically significant.
-
B.
wasFirstIdentifiedAsVolcanoBy
Indicates that an entity was initially recognized or classified as a volcano by a specific agent or source.
-
C.
eruptiveCenterOf
chosen
Indicates that one entity is the source or focal point from which a volcanic or eruptive event originates for another entity.
-
D.
eruptionName
Indicates the specific name assigned to a volcanic eruption event associated with an entity.
-
E.
eruptionStartDate
Indicates the date on which an eruption event begins.
- 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_69bd4468aacc8190a8196f71855cdf4f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b4c6fa8819099442b1b110e51fb |
completed | March 20, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69bd77c1397c8190a7fd844d7a396e54 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:49 p.m.