Triple
T34173169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | York–Scarborough line |
E876595
|
entity |
| Predicate | nonElectrified |
P21804
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [York–Scarborough line, nonElectrified, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nonElectrified Context triple: [York–Scarborough line, nonElectrified, true]
-
A.
nonElectrifiedSection
chosen
Indicates that a segment of a transportation or track network lacks electrical infrastructure for powered operation.
-
B.
isElectrically
Indicates that one entity has an electrical property, connection, or interaction in relation to another entity.
-
C.
isElectricRailway
Indicates that a given railway system operates using electric power rather than diesel or other forms of propulsion.
-
D.
isElectrifiedSince
Indicates that an entity has had electrical power or electrification continuously from a specified point in time onward.
-
E.
nonConductingDirection
Indicates a directional relationship along which conduction (such as electrical or thermal flow) does not occur or is blocked between entities.
- 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_69f349ad97ac8190bf1f17417c970e64 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70fe65ff88190885d58d51c200108 |
completed | May 3, 2026, 9:05 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:54 a.m.