Triple
T31452873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hope Street, Glasgow |
E802369
|
entity |
| Predicate | hasBusCorridorFunction |
P58541
|
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: [Hope Street, Glasgow, hasBusCorridorFunction, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBusCorridorFunction Context triple: [Hope Street, Glasgow, hasBusCorridorFunction, yes]
-
A.
hasBusServices
Indicates that one location or entity is served by bus routes or bus transportation provided by another.
-
B.
hasPublicTransitFunction
chosen
Indicates that something serves a role or provides a service related to public transportation operations or infrastructure.
-
C.
hasChronobusLine
Indicates that a location or entity is served by, or connected to, a Chronobus transit line.
-
D.
hasRERConnectionCorridor
Indicates that there exists a physical corridor connection between entities within the RER (Regional Express Network) system.
-
E.
isGatewayCorridorFor
Indicates that something serves as a primary access route or passageway enabling movement or connection to another place, system, or area.
- 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_69f348c678ac81908a2e950867619061 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: April 30, 2026, 9:14 p.m.