Triple
T31883025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cradley Heath railway station |
E813930
|
entity |
| Predicate | hasBusInterchangeWith |
P2423
|
FINISHED |
| Object | local bus services |
—
|
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: local bus services | Statement: [Cradley Heath railway station, hasBusInterchangeWith, local bus services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBusInterchangeWith Context triple: [Cradley Heath railway station, hasBusInterchangeWith, local bus services]
-
A.
hasBusInterchange
chosen
Indicates that one transport-related entity includes, contains, or is associated with a bus interchange facility.
-
B.
hasInterchangeStationWith
Indicates that two transportation lines, routes, or systems share a station where passengers can transfer between them.
-
C.
hasBusStation
Indicates that a place or area contains or is served by a bus station.
-
D.
hasBusTerminalType
Indicates the specific category or type of bus terminal associated with an entity.
-
E.
hasNearbyInterchange
Indicates that one location has a transportation interchange (such as a junction or transfer point) situated close to it.
- 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_69f348ed74bc81909846aaa6a3c7318c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: April 30, 2026, 11:56 p.m.