Triple
T27760375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quarto |
E701450
|
entity |
| Predicate | nearVolcanicArea |
P10443
|
FINISHED |
| Object | Campi Flegrei |
—
|
NE NERFINISHED |
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: Campi Flegrei | Statement: [Quarto, nearVolcanicArea, Campi Flegrei]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearVolcanicArea Context triple: [Quarto, nearVolcanicArea, Campi Flegrei]
-
A.
nearVolcano
chosen
Indicates that one entity is located in close proximity to a volcano.
-
B.
volcanoTypeNearby
Indicates that one entity is located near another entity that is classified as a particular type of volcano.
-
C.
containsVolcanicRegion
Indicates that one entity geographically includes or encompasses an area characterized by volcanic features or activity.
-
D.
isVolcanicNeighborOf
Indicates that one geographic feature is located close enough to another volcanic feature that they are considered neighboring volcano-related entities.
-
E.
volcanicRiskArea
Indicates that a location lies within an area exposed to potential hazards from volcanic activity, such as eruptions, ashfall, or lava flows.
- 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63765603c8190a782bd8139a5a862 |
completed | May 2, 2026, 5:41 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 4:26 p.m.