Triple
T26431019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sandhurst railway station |
E664508
|
entity |
| Predicate | distanceFromGatwickAirport |
P58933
|
FINISHED |
| Object | approximately 30 miles by rail |
—
|
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 30 miles by rail | Statement: [Sandhurst railway station, distanceFromGatwickAirport, approximately 30 miles by rail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromGatwickAirport Context triple: [Sandhurst railway station, distanceFromGatwickAirport, approximately 30 miles by rail]
-
A.
distanceToGatwickAirport
chosen
Indicates the measured distance between a given entity’s location and Gatwick Airport.
-
B.
distanceFromHeathrow
Indicates the measured spatial distance between a given entity and Heathrow.
-
C.
distanceFromCentralLondon
Indicates the spatial separation or length of travel between a given location and central London.
-
D.
distanceToStanstedAirport
Indicates the physical distance between a given location or entity and Stansted Airport.
-
E.
distanceToLondon
Indicates the measured distance between a given entity’s location and the city of 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_69ee883ad6a4819088f918e76122d690 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69fe2f078c24819082ba396b56f02808 |
completed | May 8, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69fe228fe1988190baf3bb34897f3dbe |
completed | May 8, 2026, 5:51 p.m. |
Created at: April 26, 2026, 11:49 p.m.