Triple
T7869545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phlegraean Fields volcanic system |
E182703
|
entity |
| Predicate | NeapolitanYellowTuffDepositType |
P50412
|
FINISHED |
| Object | welded tuff |
—
|
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: welded tuff | Statement: [Phlegraean Fields volcanic system, NeapolitanYellowTuffDepositType, welded tuff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NeapolitanYellowTuffDepositType Context triple: [Phlegraean Fields volcanic system, NeapolitanYellowTuffDepositType, welded tuff]
-
A.
typicalLavaType
Indicates the usual or characteristic type of lava associated with a given volcanic feature, eruption, or context.
-
B.
geologicType
chosen
Indicates the specific geological classification or category assigned to a rock, soil, or earth material unit.
-
C.
tephraName
Indicates that one entity is the designated name or label assigned to a specific tephra (volcanic ash or pyroclastic) unit.
-
D.
crustType
Indicates the specific style or form of crust associated with an item, such as a pizza or baked good.
-
E.
hasPyroclasticDeposits
Indicates that an entity exhibits or contains accumulations of pyroclastic volcanic material deposited by explosive eruptions.
- 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_69ca82894d9081908a832bfce71a4714 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3848d6d88190830afcf04ad12154 |
completed | March 31, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69cae925ca388190ae4a01fa76e957e8 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:55 p.m.