Triple
T24359497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiverton Parkway railway station |
E614015
|
entity |
| Predicate | distanceFromTiverton |
P155914
|
FINISHED |
| Object | approximately 6 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 6 miles | Statement: [Tiverton Parkway railway station, distanceFromTiverton, approximately 6 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromTiverton Context triple: [Tiverton Parkway railway station, distanceFromTiverton, approximately 6 miles]
-
A.
distanceToTaunton
Indicates the spatial distance between a given entity and the location Taunton.
-
B.
distanceFromWestport
Indicates the measured distance between a given location and the reference place named Westport.
-
C.
distanceToTruro
Indicates the measured spatial distance between a given location or entity and the place named Truro.
-
D.
distanceToHartford
Indicates the spatial distance between a given entity’s location and the city of Hartford.
-
E.
distanceToProvidence
Indicates the measured spatial distance between a given entity’s location and the location of Providence.
- 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_69e2d7dfe7f08190b7a1f3a36483ab05 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2934bcc608190b86bc091474bb259 |
completed | April 29, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2 a.m.