Triple
T26230169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Kilbride branch line |
E656012
|
entity |
| Predicate | connectsWithNetworkAt |
P37306
|
FINISHED |
| Object | Glasgow Central |
—
|
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 | Statement: [East Kilbride branch line, connectsWithNetworkAt, Glasgow Central]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsWithNetworkAt Context triple: [East Kilbride branch line, connectsWithNetworkAt, Glasgow Central]
-
A.
connectsWithin
Indicates that one entity establishes a connection or link between elements that lie inside the bounds or scope of another entity.
-
B.
connectedToNationalNetworkAt
Indicates that an entity has a direct linkage or access point to a broader national-level network or infrastructure.
-
C.
connectsState
Indicates a relationship where one entity serves as a link or conduit between different states, conditions, or statuses of another entity.
-
D.
connectionTo
chosen
Indicates a relationship in which one entity is linked, associated, or otherwise related to another entity.
-
E.
partOfNetworkSince
Indicates that an entity has been a member or component of a particular network starting from a specified point in time.
- 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_69ee5b4b8b408190993da38c0067cc8d |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 26, 2026, 8:59 p.m.