Triple
T13711948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ryde Esplanade railway station |
E328792
|
entity |
| Predicate | distanceFromRydeStJohnsRoad |
P111284
|
FINISHED |
| Object | approximately 0.75 miles |
—
|
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 0.75 miles | Statement: [Ryde Esplanade railway station, distanceFromRydeStJohnsRoad, approximately 0.75 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromRydeStJohnsRoad Context triple: [Ryde Esplanade railway station, distanceFromRydeStJohnsRoad, approximately 0.75 miles]
-
A.
distanceFromStJohns
Indicates the measured distance between a given location and St. Johns.
-
B.
distanceFromBathurst
Indicates the spatial distance between a given entity and the reference location Bathurst.
-
C.
distanceToJindabyneByRoad
Indicates the length of the route between an entity and Jindabyne when traveling via the road network.
-
D.
distanceToKingstonApprox
Indicates an approximate distance between a given location and Kingston.
-
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. chosen
Provenance (4 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_69d80770b9bc81909f70c8c317d53cff |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dd4395e8c0819098719c8cd344aa33 |
completed | April 13, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69dbbe92d77c81908e0244cffb7f78c5 |
completed | April 12, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69dbc59ca1a88190a6abd3bd00554c93 |
completed | April 12, 2026, 4:17 p.m. |
Created at: April 9, 2026, 9:54 p.m.