Triple
T32143688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strongyle |
E820970
|
entity |
| Predicate | eruptionKnownAs |
P35492
|
FINISHED |
| Object | Minoan eruption |
—
|
NE NERFINISHED |
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: Minoan eruption | Statement: [Strongyle, eruptionKnownAs, Minoan eruption]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eruptionKnownAs Context triple: [Strongyle, eruptionKnownAs, Minoan eruption]
-
A.
eruptionName
chosen
Indicates the specific name assigned to a volcanic eruption event associated with an entity.
-
B.
eruptionObserved
Indicates that an eruption event has been witnessed, detected, or recorded by an observer or observing system.
-
C.
eruptionVolcano
Indicates that a volcanic eruption event is occurring at or is associated with a specific volcano.
-
D.
notableEruption
Indicates that a volcano or geothermal feature has experienced an eruption considered historically or scientifically significant.
-
E.
eruptionFocus
Indicates that an eruption event is centered on, originates from, or is primarily associated with a particular focal location or feature.
- 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_69f3490520d081909b2f1271dab75faa |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b9b17d908190a6bfa2f8b5402f1e |
completed | May 3, 2026, 2:57 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:31 a.m.