Triple
T23798431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peartree railway station |
E588601
|
entity |
| Predicate | distanceFromDerbyStation |
P61200
|
FINISHED |
| Object | a short distance south of Derby railway station |
—
|
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: a short distance south of Derby railway station | Statement: [Peartree railway station, distanceFromDerbyStation, a short distance south of Derby railway station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromDerbyStation Context triple: [Peartree railway station, distanceFromDerbyStation, a short distance south of Derby railway station]
-
A.
distanceToDerby
chosen
Indicates the spatial distance between an entity and the location named Derby.
-
B.
distanceFromStation
Indicates the measured spatial separation between an entity and a specified station.
-
C.
distanceFromSouthStation
Indicates the measured distance between a given location or entity and South Station.
-
D.
distanceFromLiverpoolStreet
Indicates the measured distance between a given location and Liverpool Street.
-
E.
distanceToYorkCityCentre
Indicates the measured or specified distance between a given location and the centre of York city.
- 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_69e25d15db58819092ac1e6791696fd9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c6dea2888190b3ff1c96da5cfefb |
completed | April 29, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:51 p.m.