Triple
T31211525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maipo volcano |
E795754
|
entity |
| Predicate | isBoundaryMarkerBetween |
P39423
|
FINISHED |
| Object | Chile |
—
|
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: Chile | Statement: [Maipo volcano, isBoundaryMarkerBetween, Chile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBoundaryMarkerBetween Context triple: [Maipo volcano, isBoundaryMarkerBetween, Chile]
-
A.
isBoundaryFor
Indicates that one entity serves as the limiting edge, border, or enclosing extent that defines the spatial or conceptual bounds of another entity.
-
B.
hasBorderMarkerType
Indicates that a border marker possesses or is classified by a specific type or category of border marker.
-
C.
wasDemarcatedBetween
Indicates that a boundary or dividing line was formally established separating one entity from another.
-
D.
borderDefinedBetween
Indicates that a boundary line or border is formally established between two geographic or political entities.
-
E.
boundaryBetween
chosen
Indicates that something serves as a dividing line or limit separating two distinct regions, areas, or entities.
- 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_69f224d9d52c8190a61f68ded37fa755 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c27f0bc8190b2da3a8b9791271a |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f696673214819094350e1d2648ef34 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:09 p.m.