Triple
T31841167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beverley Road station |
E812805
|
entity |
| Predicate | hasAdjacentExpressTracks |
P74866
|
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: [Beverley Road station, hasAdjacentExpressTracks, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdjacentExpressTracks Context triple: [Beverley Road station, hasAdjacentExpressTracks, yes]
-
A.
hasExpressTracks
Indicates that a transportation route or facility includes tracks designated for express service, allowing faster travel with fewer stops than regular tracks.
-
B.
hasAdjacentRailService
Indicates that one location has rail service situated directly next to or immediately bordering it.
-
C.
hasCenterExpressTracks
chosen
Indicates that the subject location or facility contains express railway tracks running through its central area or core.
-
D.
hasAdjacentStations
Indicates that two stations are directly next to each other in a sequence or network, with no other station in between.
-
E.
hasHighSpeedLine
Indicates that there exists a high-speed rail line connection between the related entities.
- 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_69f348ea7ffc8190a2ab43d80277cf59 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: April 30, 2026, 11:49 p.m.