Triple
T11814132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Town Hall railway station |
E280952
|
entity |
| Predicate | hasNightBusConnections |
P39381
|
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: [Town Hall railway station, hasNightBusConnections, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNightBusConnections Context triple: [Town Hall railway station, hasNightBusConnections, yes]
-
A.
hasPublicTransportConnection
Indicates that there is an available public transportation link or service connecting the related entities.
-
B.
hasBusServices
chosen
Indicates that one location or entity is served by bus routes or bus transportation provided by another.
-
C.
isPublicTransport
Indicates that the entity functions as a mode or instance of transportation that is available for use by the general public, typically operating on fixed routes or schedules.
-
D.
isPublicTransportBackboneOf
Indicates that one transport system serves as the primary structural and functional core of a region’s overall public transportation network.
-
E.
hasTrolleybusLine
Indicates that there exists a trolleybus service or route connecting 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_69d6ab26aae88190b2489efcb2a24234 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a658f918819092c2db05fe2ab0ce |
completed | April 10, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69d8a24e9a088190aff7932d1ff93dbf |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.