Triple
T25147543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Box Hill railway station |
E629975
|
entity |
| Predicate | hasBusTerminalAbove |
P2423
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Box Hill railway station, hasBusTerminalAbove, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBusTerminalAbove Context triple: [Box Hill railway station, hasBusTerminalAbove, yes]
-
A.
hasPassengerTerminal
Indicates that one entity possesses or is equipped with a passenger terminal used for boarding, alighting, or handling passengers.
-
B.
hasBusInterchange
chosen
Indicates that one transport-related entity includes, contains, or is associated with a bus interchange facility.
-
C.
hasBusStation
Indicates that a place or area contains or is served by a bus station.
-
D.
hasBusPlatforms
Indicates that a location or facility is equipped with one or more designated platforms for boarding or alighting from buses.
-
E.
hasMetroTerminus
Indicates that one location serves as the terminal (end) station of a metro line for another location.
- 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_69e2ff349e408190a6f4a5a66279f54d |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f4684e47988190a5c0639fc7fc21e8 |
completed | May 1, 2026, 8:46 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 6:30 a.m.