Triple
T5391821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bradford Interchange |
E120346
|
entity |
| Predicate | hasBusStationType |
P27765
|
FINISHED |
| Object | enclosed bus concourse |
—
|
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: enclosed bus concourse | Statement: [Bradford Interchange, hasBusStationType, enclosed bus concourse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBusStationType Context triple: [Bradford Interchange, hasBusStationType, enclosed bus concourse]
-
A.
hasBusStation
Indicates that a place or area contains or is served by a bus station.
-
B.
hasRailStation
Indicates that one entity possesses, contains, or is served by a rail station.
-
C.
hasBusPlatforms
Indicates that a location or facility is equipped with one or more designated platforms for boarding or alighting from buses.
-
D.
isPublicTransportStation
Indicates that a location functions as a station or stop used by public transportation services such as buses, trains, trams, or subways.
-
E.
stationType
chosen
Indicates the specific category or classification of a station based on its function, services, or operational characteristics.
- 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_69bd46354c648190a38b26f107010a96 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd8719ff04819089e3a90f90b5e3fc |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd8463a9c88190bd760378f3026180 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:04 p.m.