Triple
T299142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deccan Traps volcanism |
E6159
|
entity |
| Predicate | eruptedFrom |
P6355
|
FINISHED |
| Object | numerous fissure vents |
—
|
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: numerous fissure vents | Statement: [Deccan Traps volcanism, eruptedFrom, numerous fissure vents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eruptedFrom Context triple: [Deccan Traps volcanism, eruptedFrom, numerous fissure vents]
-
A.
notableEruption
Indicates that a volcano or geothermal feature has experienced an eruption considered historically or scientifically significant.
-
B.
lastEruption
Indicates the time or event corresponding to the most recent eruption associated with a given entity.
-
C.
volcanicOrigin
chosen
Indicates that something originates from, is produced by, or is directly associated with volcanic activity or processes.
-
D.
volcanismType
Indicates the specific kind or style of volcanic activity or processes associated with an entity.
-
E.
emergedFrom
Indicates that one entity originated, arose, or came forth from another entity or source.
- 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_69a2e79114b081909490b3bf5a5dbb51 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea0dd1dc8190aecd5afdeb2fd74b |
completed | Feb. 28, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69a2e9398df08190af40063a2de7a1d0 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.