Triple
T36530988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brunovistulian terrane |
E900441
|
entity |
| Predicate | hasMagmatismAge |
P28561
|
FINISHED |
| Object | Neoproterozoic 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: Neoproterozoic magmatism | Statement: [Brunovistulian terrane, hasMagmatismAge, Neoproterozoic magmatism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMagmatismAge Context triple: [Brunovistulian terrane, hasMagmatismAge, Neoproterozoic magmatism]
-
A.
hasMagmatismSource
Indicates that something has a source or origin related to magmatic activity, such as magma generation or movement within the Earth.
-
B.
volcanicFieldAge
chosen
Indicates the age or geological time period during which a volcanic field formed or was active.
-
C.
notableEruptionAge
Indicates the age or time period at which a notable volcanic eruption associated with an entity occurred.
-
D.
hasSeafloorAge
Indicates the age of a specified portion of the seafloor relative to a given time or reference point.
-
E.
magmaticVolume
Indicates the amount of magma involved or produced in a magmatic process or event.
- 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_69f76e5fbb388190b70c4c15573c8143 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a03446ec72881909c5ff25a48baadb3 |
completed | May 12, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_6a03439b393c819084aa9b7ed0d5b6b0 |
completed | May 12, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:11 p.m.