Triple
T10783342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cocos Plate large igneous province |
E254385
|
entity |
| Predicate | eruptionEnvironment |
P70535
|
FINISHED |
| Object | deep-sea floor |
—
|
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: deep-sea floor | Statement: [Cocos Plate large igneous province, eruptionEnvironment, deep-sea floor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eruptionEnvironment Context triple: [Cocos Plate large igneous province, eruptionEnvironment, deep-sea floor]
-
A.
eruptiveEnvironment
chosen
Indicates the geological or environmental setting in which an eruption or eruptive activity occurs.
-
B.
eruptionMechanism
Indicates the physical process or mechanism by which an eruption occurs or is driven.
-
C.
eruptionImpact
Indicates the effects or consequences that a volcanic eruption has on surrounding entities, environments, or systems.
-
D.
eruptionFormed
Indicates that one entity was created or brought into existence as a direct result of a volcanic eruption involving the other entity.
-
E.
eruptionEffect
Indicates the impact or consequences that an eruption has on its surrounding environment, systems, or entities.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d732d1b4bc8190871dd21265065705 |
completed | April 9, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69d6f316940c819092a96c429629fdef |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:17 p.m.