Triple
T11262874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plattsburgh International Airport |
E266608
|
entity |
| Predicate | distanceFromMontreal |
P89770
|
FINISHED |
| Object | approximately 60 miles south |
—
|
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: approximately 60 miles south | Statement: [Plattsburgh International Airport, distanceFromMontreal, approximately 60 miles south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromMontreal Context triple: [Plattsburgh International Airport, distanceFromMontreal, approximately 60 miles south]
-
A.
distanceToMontreal
chosen
Indicates the spatial distance between a given entity’s location and the city of Montreal.
-
B.
distanceFromQuebecCityCentre
Indicates the measured spatial distance between a given location and the center of Quebec City.
-
C.
distanceFromToronto
Indicates the spatial distance between a given entity and the location of Toronto.
-
D.
distanceToOttawa
Indicates the spatial distance between a given entity’s location and the city of Ottawa.
-
E.
distanceToOttawaByRoad
Indicates the length of the travel route between a place and Ottawa when moving along the road network rather than in a straight line.
- 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_69d6aac7953c8190b82caf9d7640fdf9 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e94c066c8190be1e032eb328e5fe |
completed | April 9, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69d7879bc56c8190b2e8d2193f29de05 |
completed | April 9, 2026, 11:03 a.m. |
Created at: April 8, 2026, 9:31 p.m.