Triple
T24359072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thornford railway station |
E614005
|
entity |
| Predicate | distanceFromYeovilPenMill |
P102359
|
FINISHED |
| Object | approximately 3 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 3 miles | Statement: [Thornford railway station, distanceFromYeovilPenMill, approximately 3 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromYeovilPenMill Context triple: [Thornford railway station, distanceFromYeovilPenMill, approximately 3 miles]
-
A.
distanceToYeovil
chosen
Indicates the spatial distance between a given entity or location and the town of Yeovil.
-
B.
distanceToPenzance
Indicates the spatial distance between a given entity’s location and the town of Penzance.
-
C.
distanceFromLiskeard
Indicates the measured distance between a given location and the town of Liskeard.
-
D.
distanceFromPoole
Indicates the spatial distance between a given entity and the location Poole.
-
E.
distanceFromWarminster
Indicates the spatial distance between a given entity or location and Warminster.
- 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_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. |
Created at: April 18, 2026, 2 a.m.