Triple
T15539456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Arctic Large Igneous Province |
E370437
|
entity |
| Predicate | magmaticOrigin |
P6355
|
FINISHED |
| Object | mantle plume activity (hypothesized) |
—
|
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: mantle plume activity (hypothesized) | Statement: [High Arctic Large Igneous Province, magmaticOrigin, mantle plume activity (hypothesized)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: magmaticOrigin Context triple: [High Arctic Large Igneous Province, magmaticOrigin, mantle plume activity (hypothesized)]
-
A.
volcanicOrigin
chosen
Indicates that something originates from, is produced by, or is directly associated with volcanic activity or processes.
-
B.
magmaticVolume
Indicates the amount of magma involved or produced in a magmatic process or event.
-
C.
volcanismType
Indicates the specific kind or style of volcanic activity or processes associated with an entity.
-
D.
volcanoComposition
Indicates that a volcano is composed of, or primarily made up of, a specified material or set of materials.
-
E.
volcanic
Indicates that an entity is characterized by or associated with volcanic activity, materials, or processes.
- 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04430b5188190a555a3cd4fb0c61c |
completed | April 16, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69deda7a95c48190bbe29fadcf17191a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:07 a.m.