Triple
T26261616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Morang |
E656862
|
entity |
| Predicate | railExtension |
P30642
|
FINISHED |
| Object | Mernda line extension opened 2018 |
—
|
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: Mernda line extension opened 2018 | Statement: [South Morang, railExtension, Mernda line extension opened 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railExtension Context triple: [South Morang, railExtension, Mernda line extension opened 2018]
-
A.
lightRailExpansion
Indicates the process or plan of extending an existing light rail transit system to cover additional areas or routes.
-
B.
railTracks
Indicates that one entity consists of, includes, or is associated with rail tracks used for guiding trains or rail vehicles.
-
C.
railwayLine
Indicates that there is a railway line connection or route associated with or passing through the referenced entity.
-
D.
hasRailwayLineUnderConstruction
Indicates that a railway line associated with an entity is currently in the process of being built but not yet completed.
-
E.
railwayLineOpened
chosen
Indicates that a railway line began official operation or service on a specified date.
- 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_69ee5b4e21bc819082be98bc9ab09796 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f60e00b03c81909d04a9821907dc0d |
completed | May 2, 2026, 2:45 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 9:10 p.m.