Triple
T13843338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Cabeza |
E332724
|
entity |
| Predicate | relativePositionOnVolcano |
P44470
|
FINISHED |
| Object | northern sector |
—
|
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: northern sector | Statement: [La Cabeza, relativePositionOnVolcano, northern sector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativePositionOnVolcano Context triple: [La Cabeza, relativePositionOnVolcano, northern sector]
-
A.
nearVolcano
Indicates that one entity is located in close proximity to a volcano.
-
B.
locatedInCalderaOf
Indicates that one entity is situated within the caldera (the large volcanic crater) of another entity.
-
C.
positionRelativeToSummit
chosen
Indicates the spatial relationship of an entity’s location with respect to the summit of a feature or structure.
-
D.
isVolcanicEdificeOn
Indicates that a volcanic edifice is physically located on or built upon a specified surface or geological feature.
-
E.
associatedVolcano
Indicates that there is a specific volcano linked or connected to the referenced entity, such as by location, impact, or relevance.
- 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_69d81c5ba13c8190839315f54768acfd |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02afce788190a74dce4e6a3569fa |
completed | April 14, 2026, 9:02 a.m. |
| PD | Predicate disambiguation | batch_69dbc8691b608190a25a7c70a366b170 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:13 p.m.