Triple
T23927964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Gwillimbury GO Station |
E602410
|
entity |
| Predicate | distanceFromTorontoUnionStation |
P23260
|
FINISHED |
| Object | approximately 60 km north (approximate) |
—
|
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 km north (approximate) | Statement: [East Gwillimbury GO Station, distanceFromTorontoUnionStation, approximately 60 km north (approximate)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromTorontoUnionStation Context triple: [East Gwillimbury GO Station, distanceFromTorontoUnionStation, approximately 60 km north (approximate)]
-
A.
distanceFromToronto
Indicates the spatial distance between a given entity and the location of Toronto.
-
B.
distanceToToronto
chosen
Indicates the spatial distance between a given entity’s location and the city of Toronto.
-
C.
distanceToTorontoPearsonInternationalAirport
Indicates the physical distance between a given location and Toronto Pearson International Airport.
-
D.
distanceToOttawa
Indicates the spatial distance between a given entity’s location and the city of Ottawa.
-
E.
distanceFromWaterloo
Indicates the spatial distance between a given location and Waterloo.
- 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_69e2953b928c819095395fa87baca583 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cf1efb348190b4cbb32b3b6c9ae4 |
completed | April 29, 2026, 9:27 a.m. |
| PD | Predicate disambiguation | batch_69f16151ebdc819086e9e1d7cc1f4f3c |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:49 p.m.