Triple
T20273698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Atlantic volcanic province |
E502955
|
entity |
| Predicate | magmaticAffinity |
P80028
|
FINISHED |
| Object | intraplate basaltic magmatism |
—
|
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: intraplate basaltic magmatism | Statement: [North Atlantic volcanic province, magmaticAffinity, intraplate basaltic magmatism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: magmaticAffinity Context triple: [North Atlantic volcanic province, magmaticAffinity, intraplate basaltic magmatism]
-
A.
hasMagmaComposition
chosen
Indicates that something possesses or is characterized by a specific magma composition.
-
B.
hasTectonicAffinity
Indicates a relationship where one geological unit or feature shares a common tectonic origin, setting, or structural association with another.
-
C.
magmaticVolume
Indicates the amount of magma involved or produced in a magmatic process or event.
-
D.
mantleType
Indicates the type or classification of a mantle associated with an entity, specifying what kind of mantle it has.
-
E.
lavaViscosity
Indicates the thickness or resistance to flow of lava in a volcanic or geological context.
- 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_69e0b4b0e79c8190bd61f22ef1329fa8 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e675e104f081909d17c1963a5db528 |
completed | April 20, 2026, 6:52 p.m. |
| PD | Predicate disambiguation | batch_69e55b1e5e1c8190ba8a5544b1db9e1d |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 10:28 a.m.