Triple
T24753659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mekoryuk Airport |
E619217
|
entity |
| Predicate | nearby settlement |
P138521
|
FINISHED |
| Object | village of Mekoryuk |
—
|
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: village of Mekoryuk | Statement: [Mekoryuk Airport, nearby settlement, village of Mekoryuk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearby settlement Context triple: [Mekoryuk Airport, nearby settlement, village of Mekoryuk]
-
A.
nearbySettlements
chosen
Indicates that one settlement is located close to another settlement in geographic space.
-
B.
nearbySettlementRegion
Indicates that a settlement is located close to or within the surrounding area of a specified region.
-
C.
hasNearestLargerSettlement
Indicates that one settlement is associated with the geographically closest settlement that is larger in size or population.
-
D.
hasNearbyTown
Indicates that one location has a town situated close to it in geographic proximity.
-
E.
nearbySettlementUS
Indicates that one settlement is geographically close to another settlement within the United States.
- 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_69e2fabb349881908a13a212a0221a63 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cf017a88190b4985b11159c907d |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 4:25 a.m.