Triple
T30875400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kimberley kimberlite fields |
E786462
|
entity |
| Predicate | eruptedThrough |
P170588
|
FINISHED |
| Object | diatremes |
—
|
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: diatremes | Statement: [Kimberley kimberlite fields, eruptedThrough, diatremes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eruptedThrough Context triple: [Kimberley kimberlite fields, eruptedThrough, diatremes]
-
A.
erupted
Indicates that a volcano or similar geological feature suddenly expelled lava, ash, gas, or other material in a violent outburst.
-
B.
eruptionFormed
Indicates that one entity was created or brought into existence as a direct result of a volcanic eruption involving the other entity.
-
C.
eruptionSeriesOf
Indicates a relationship where a specific volcanic eruption is a member event within a broader series or sequence of related eruptions.
-
D.
eruptionVolcano
Indicates that a volcanic eruption event is occurring at or is associated with a specific volcano.
-
E.
eruptionTrigger
Indicates that one event, condition, or action causes or initiates an eruption of another entity or system.
- F. None of above. chosen
Provenance (4 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_69f224bae17c8190bb3a6a28e3d019df |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f691d56ec081909265c4b014388243 |
completed | May 3, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68fb914b88190b0cad83ea9fe9dfc |
completed | May 2, 2026, 11:58 p.m. |
Created at: April 29, 2026, 8:48 p.m.