Triple
T7869568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phlegraean Fields volcanic system |
E182703
|
entity |
| Predicate | partlySubmerged |
P44338
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Phlegraean Fields volcanic system, partlySubmerged, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partlySubmerged Context triple: [Phlegraean Fields volcanic system, partlySubmerged, true]
-
A.
partiallySubmerged
chosen
Indicates that one entity is located such that only a portion of it is below the surface of a surrounding medium (typically a liquid), while the rest remains above.
-
B.
submerged
Indicates that one entity is located beneath the surface of a liquid or other surrounding medium, typically fully covered by it.
-
C.
submergedBy
Indicates that one entity is covered or overwhelmed by liquid, typically water, to the point of being beneath its surface due to the action or presence of another entity.
-
D.
displacementSubmerged
Indicates the amount of fluid displaced by an object when it is submerged.
-
E.
submergedFeatures
Indicates that certain features or elements are located beneath the surface of a body of water or otherwise covered by liquid.
- 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.