Triple
T12150285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Momotombito Island |
E289433
|
entity |
| Predicate | proximityRelation |
P45695
|
FINISHED |
| Object | close to Momotombo Volcano |
—
|
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: close to Momotombo Volcano | Statement: [Momotombito Island, proximityRelation, close to Momotombo Volcano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proximityRelation Context triple: [Momotombito Island, proximityRelation, close to Momotombo Volcano]
-
A.
spatialRelation
Indicates a spatial relationship between entities, specifying how one is positioned or located relative to another in space.
-
B.
nearbyTo
Indicates that one entity is located close in distance or position to another entity.
-
C.
isCloseTo
chosen
Indicates that one entity is physically or conceptually near another, within a relatively short distance or range.
-
D.
featuresRegionalProximity
Indicates that one entity is located near or in close geographic proximity to a particular region or another entity.
-
E.
nearPass
Indicates that one entity moves or travels close to another entity without necessarily making direct contact or interaction.
- 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_69d6ab4c6710819097a9d228382dde43 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d915d7109481908bf5fe512bba3c89 |
completed | April 10, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69d9150c18148190bf8152189c0e5fca |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:49 p.m.