Triple
T4431407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Clyde Line |
E95337
|
entity |
| Predicate | openedAsElectrifiedRoute |
P55966
|
FINISHED |
| Object | 1960 |
—
|
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: 1960 | Statement: [North Clyde Line, openedAsElectrifiedRoute, 1960]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsElectrifiedRoute Context triple: [North Clyde Line, openedAsElectrifiedRoute, 1960]
-
A.
openedRouteThrough
Indicates that one entity has created or established a passage, connection, or pathway that allows movement or access through another entity or area.
-
B.
openedAsRailStop
Indicates that an entity began operation or was first established specifically as a railway stop.
-
C.
isElectricRailway
Indicates that a given railway system operates using electric power rather than diesel or other forms of propulsion.
-
D.
openedAsThroughRoute
Indicates that a route or service began operating as a continuous through connection, rather than as separate or terminating segments.
-
E.
openedAsExpresswaySection
Indicates that a particular section of roadway was inaugurated and began operation specifically as an expressway segment.
- F. None of above. chosen
Provenance (4 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_69b3453c2a0c8190926b574c90766db9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3556b71448190a3fab938853f8b87 |
completed | March 13, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69b34f6078cc8190831b89f404198cc5 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b3505a87b4819083fbbd58870e520b |
completed | March 12, 2026, 11:46 p.m. |
Created at: March 12, 2026, 11:31 p.m.