Triple
T13077020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vulcanian eruption |
E329604
|
entity |
| Predicate | ejects |
P49676
|
FINISHED |
| Object | volcanic ash |
—
|
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: volcanic ash | Statement: [Vulcanian eruption, ejects, volcanic ash]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ejects Context triple: [Vulcanian eruption, ejects, volcanic ash]
-
A.
canEject
Indicates that one entity has the ability or permission to forcibly remove or expel another entity from a place, system, or context.
-
B.
hasEjecta
chosen
Indicates that one entity produces or is associated with material expelled or thrown out from another entity as a result of an energetic event or process.
-
C.
expel
Indicates forcing an entity to leave or be removed from a place, group, or situation, typically as a punishment or consequence.
-
D.
emitted
Indicates that one entity has released, discharged, or sent out another entity, such as energy, particles, signals, or substances, into its surroundings.
-
E.
εκβάλλειΣτο
Indicates that one geographical feature (typically a river or stream) flows into and empties into another body of water.
- 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_69d80771749c81909a6d9197b9504872 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d9811828448190ac6ddd3e9c221251 |
completed | April 10, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69d9803d46688190bac6b7d208f08d01 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:01 p.m.