Triple
T6692316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milwaukee Road |
E152656
|
entity |
| Predicate | electrificationBegan |
P59370
|
FINISHED |
| Object | 1914 |
—
|
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: 1914 | Statement: [Milwaukee Road, electrificationBegan, 1914]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electrificationBegan Context triple: [Milwaukee Road, electrificationBegan, 1914]
-
A.
electrificationYear
chosen
Indicates the year in which something (such as a system, facility, or infrastructure) was converted to or equipped for electric power.
-
B.
electrificationUsedBetween
Indicates that an electrification system or method is applied or present along the segment or connection between two entities.
-
C.
electrificationEnd
Indicates the point in time or event at which an electrification process or electrified state comes to an end.
-
D.
electrificationCompleted
Indicates that the process of providing electrical power infrastructure to the relevant entity or area has been fully completed.
-
E.
electrificationUsedFor
Indicates that electrification is employed as a means or method to achieve, enable, or support a particular function, process, or purpose.
- 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_69c6880687b08190805278b504d1c92c |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6cd0fa5188190a23281cb09d98139 |
completed | March 27, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69c6ad0d3c1081908dadff7a6a054123 |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:05 p.m.