Triple
T28865326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Filey railway station |
E728980
|
entity |
| Predicate | hasDistanceFromScarborough |
P127442
|
FINISHED |
| Object | about 7.5 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: about 7.5 miles south | Statement: [Filey railway station, hasDistanceFromScarborough, about 7.5 miles south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDistanceFromScarborough Context triple: [Filey railway station, hasDistanceFromScarborough, about 7.5 miles south]
-
A.
distanceToScarborough
chosen
Indicates the measured spatial distance between a given entity’s location and the location of Scarborough.
-
B.
distanceFromBarrie
Indicates the spatial distance separating something from the location of Barrie.
-
C.
distanceFromToronto
Indicates the spatial distance between a given entity and the location of Toronto.
-
D.
distanceToToronto
Indicates the spatial distance between a given entity’s location and the city of Toronto.
-
E.
distanceToSudbury
Indicates the spatial distance between a given entity or location and Sudbury.
- 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_69f031a01cbc8190ba87270bb6fe4639 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
Created at: April 28, 2026, 6:48 a.m.