Triple
T32206022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chilham railway station |
E822672
|
entity |
| Predicate | distanceFromAshfordInternational |
P60159
|
FINISHED |
| Object | approximately 7 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 7 miles | Statement: [Chilham railway station, distanceFromAshfordInternational, approximately 7 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromAshfordInternational Context triple: [Chilham railway station, distanceFromAshfordInternational, approximately 7 miles]
-
A.
distanceToAshford
chosen
Indicates the spatial distance between a given entity and the location named Ashford.
-
B.
distanceFromHeathrow
Indicates the measured spatial distance between a given entity and Heathrow.
-
C.
distanceToGatwickAirport
Indicates the measured distance between a given entity’s location and Gatwick Airport.
-
D.
distanceToAirport
Indicates the measured distance between a given location and the nearest or specified airport.
-
E.
distanceToManchesterAirport
Indicates the spatial distance between a given location or entity and Manchester Airport.
- 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_69f349093174819086e633c190a51aa8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a0340784c488190aa6c7c9be2e8a434 |
completed | May 12, 2026, 3 p.m. |
| PD | Predicate disambiguation | batch_6a033f33eddc819091507716f6ed7d7d |
completed | May 12, 2026, 2:54 p.m. |
Created at: May 1, 2026, 12:36 a.m.