Triple
T30973524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gillingham, Dorset |
E789163
|
entity |
| Predicate | distanceToLondonWaterlooByRail |
P39021
|
FINISHED |
| Object | approximately 2 hours |
—
|
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 2 hours | Statement: [Gillingham, Dorset, distanceToLondonWaterlooByRail, approximately 2 hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToLondonWaterlooByRail Context triple: [Gillingham, Dorset, distanceToLondonWaterlooByRail, approximately 2 hours]
-
A.
distanceToLondon
Indicates the measured distance between a given entity’s location and the city of London.
-
B.
distanceFromLiverpoolStreet
Indicates the measured distance between a given location and Liverpool Street.
-
C.
lineDistanceFromLondonKingsCross
Indicates the distance along a route or line measured from London Kings Cross as the reference starting point.
-
D.
distanceFromCentralLondon
Indicates the spatial separation or length of travel between a given location and central London.
-
E.
timeToCentralLondonByTrain
chosen
Indicates the amount of time it takes to travel by train from a given location to central London.
- 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_69f224c4831c8190be53924ec25a150a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a01839b071481909f9cc79a6a09387d |
completed | May 11, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_6a017edbed688190baa61cbae5110c8e |
completed | May 11, 2026, 7:01 a.m. |
Created at: April 29, 2026, 8:55 p.m.