Triple
T7142789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toncontín International Airport |
E166488
|
entity |
| Predicate | nearbyTerrain |
P2064
|
FINISHED |
| Object | mountains |
—
|
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: mountains | Statement: [Toncontín International Airport, nearbyTerrain, mountains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyTerrain Context triple: [Toncontín International Airport, nearbyTerrain, mountains]
-
A.
nearbyElevation
Indicates that one entity is located at or associated with an elevation that is geographically close to the elevation of another entity.
-
B.
nearbyLocation
Indicates that one location is situated close to another location in physical space.
-
C.
terrainFeature
Indicates a relationship where one entity is a natural or constructed landform or surface characteristic associated with a given location or area.
-
D.
nearbyFeature
chosen
Indicates that one entity is located close to or in the immediate vicinity of another entity.
-
E.
nearbyFrontier
Indicates that one entity is located close to a boundary or frontier region associated with another entity.
- 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_69c6888579d481909e05a8d6b81bf733 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e779ace48190be9c33750e60a79e |
completed | March 27, 2026, 8:24 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c932888190b125ca3785b18553 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:45 p.m.