Triple
T4007647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Partick subway station |
E89563
|
entity |
| Predicate | connectsWithNetwork |
P33235
|
FINISHED |
| Object | ScotRail rail network |
—
|
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: ScotRail rail network | Statement: [Partick subway station, connectsWithNetwork, ScotRail rail network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsWithNetwork Context triple: [Partick subway station, connectsWithNetwork, ScotRail rail network]
-
A.
connectsWithin
Indicates that one entity establishes a connection or link between elements that lie inside the bounds or scope of another entity.
-
B.
connectionTo
Indicates a relationship in which one entity is linked, associated, or otherwise related to another entity.
-
C.
connectsState
Indicates a relationship where one entity serves as a link or conduit between different states, conditions, or statuses of another entity.
-
D.
connectsWithMode
Indicates a relationship where one entity connects to another using a specified method, channel, or mode of connection.
-
E.
isOnNetwork
chosen
Indicates that an entity is currently connected to, accessible through, or operating within a specified network.
- 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_69aed9585e788190bec2d39deba3750f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaec08dc8190a341809059554f84 |
completed | March 9, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69aef8fa6fec81909b1190ecbba61410 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:34 p.m.