Triple
T7057751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Werribee line |
E164136
|
entity |
| Predicate | openedAsElectrifiedSuburbanLine |
P55966
|
FINISHED |
| Object | 1920s |
—
|
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: 1920s | Statement: [Werribee line, openedAsElectrifiedSuburbanLine, 1920s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsElectrifiedSuburbanLine Context triple: [Werribee line, openedAsElectrifiedSuburbanLine, 1920s]
-
A.
openedAsElectrifiedRoute
chosen
Indicates that a transportation route was inaugurated already equipped with electrification, rather than being electrified at a later time.
-
B.
openedAsSubway
Indicates that a transportation facility or line originally began operation specifically as a subway service.
-
C.
openedAsMetrolinkLine
Indicates that a railway line or route was inaugurated or began operation specifically as part of the Metrolink network.
-
D.
openedAsRedLineStation
Indicates that a station began operation specifically as part of the Red Line when it first opened.
-
E.
openedAsMetroNorthService
Indicates that a transportation facility or line began operation specifically as part of the Metro-North Railroad service.
- 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_69c68861678881909961ddf4d779f750 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e4a3c36c819080942c59f1830ae8 |
completed | March 27, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bdc1f08190975fcdbbb1854d1e |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:38 p.m.