Triple
T31452868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hope Street, Glasgow |
E802369
|
entity |
| Predicate | servesAsMainAccessTo |
P144828
|
FINISHED |
| Object | Glasgow Central station |
—
|
NE NERFINISHED |
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: Glasgow Central station | Statement: [Hope Street, Glasgow, servesAsMainAccessTo, Glasgow Central station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesAsMainAccessTo Context triple: [Hope Street, Glasgow, servesAsMainAccessTo, Glasgow Central station]
-
A.
servesAsGatewayTo
Indicates that one entity functions as an entry point, access route, or intermediary channel that enables reaching or connecting to another entity.
-
B.
mainAccessFor
chosen
Indicates that one entity serves as the primary means or route of access for another entity.
-
C.
isMainEntrance
Indicates that an entrance serves as the primary or principal access point to a place or building.
-
D.
isSecondaryEntranceOf
Indicates that one entrance serves as an additional or subordinate access point to a primary entrance of the same place or structure.
-
E.
isMajorAccessPointFor
Indicates that something serves as a primary or significant entry or connection point for accessing another entity or system.
- 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_69fecb4d02f881909a9ee97ce98000d5 |
completed | May 9, 2026, 5:51 a.m. |
| PD | Predicate disambiguation | batch_69fec9846c1c8190b317f0711f0755db |
completed | May 9, 2026, 5:43 a.m. |
Created at: April 30, 2026, 9:14 p.m.