Triple
T13334883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heathrow Central bus station |
E317662
|
entity |
| Predicate | distanceToTerminal4 |
P65220
|
FINISHED |
| Object | greater than walking distance |
—
|
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: greater than walking distance | Statement: [Heathrow Central bus station, distanceToTerminal4, greater than walking distance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToTerminal4 Context triple: [Heathrow Central bus station, distanceToTerminal4, greater than walking distance]
-
A.
distanceToTerminal
chosen
Indicates the measured or calculated distance from a given entity or location to a specified terminal point or facility.
-
B.
distanceFromTerminus
Indicates the measured distance of an entity from a defined endpoint or terminus along a route, path, or sequence.
-
C.
distanceToRailhead
Indicates the measured distance between a location or object and the nearest railhead (rail transport access point).
-
D.
distanceFromStation
Indicates the measured spatial separation between an entity and a specified station.
-
E.
terminalLocation
Indicates the specific terminal or endpoint location associated with an entity or process.
- 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_69d806b5a3c08190b42c267fb092f98a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cff44e08190b9583baf0b626e42 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6e53d88190bd6aa42f69b10ffb |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:30 p.m.