Triple
T1586096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piccadilly Gardens |
E34068
|
entity |
| Predicate | hasPublicTransportRole |
P28996
|
FINISHED |
| Object | major bus interchange |
—
|
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: major bus interchange | Statement: [Piccadilly Gardens, hasPublicTransportRole, major bus interchange]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublicTransportRole Context triple: [Piccadilly Gardens, hasPublicTransportRole, major bus interchange]
-
A.
hasPublicTransitProvider
Indicates that a place or region is served by a specific public transit operating organization or agency.
-
B.
hasPublicTransportConnection
Indicates that there is an available public transportation link or service connecting the related entities.
-
C.
hasPublicTransportStop
Indicates that a location or area contains or is served by a public transport stop, such as a bus, tram, or train stop.
-
D.
hasPublicTransportAgency
Indicates that a place or transport system is served, managed, or overseen by a specific public transportation agency.
-
E.
hasPublicTransitCoverageType
chosen
Indicates the type or category of public transit service coverage associated with an entity.
- 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_69a885fceb2c8190b47e0f7c0aefbff0 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a93aedd45c819085843ac843d640e8 |
completed | March 5, 2026, 8:12 a.m. |
| PD | Predicate disambiguation | batch_69a907bdc19081908c84c5c0aa09e282 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:27 p.m.