Triple
T4098543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helsinki Metro |
E87880
|
entity |
| Predicate | LänsimetroOpeningPhase2 |
P10389
|
FINISHED |
| Object | 2022 |
—
|
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: 2022 | Statement: [Helsinki Metro, LänsimetroOpeningPhase2, 2022]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: LänsimetroOpeningPhase2 Context triple: [Helsinki Metro, LänsimetroOpeningPhase2, 2022]
-
A.
metroLineInaugurated
chosen
Indicates that a metro line was officially opened and began operation on a specific date or during a specific event.
-
B.
railTransitLengthPlanned
Indicates the total length of rail transit infrastructure that is planned but not yet built or in operation.
-
C.
openedAsMetrolinkStop
Indicates that a location began operation specifically as a Metrolink transit stop.
-
D.
lightRailExpansion
Indicates the process or plan of extending an existing light rail transit system to cover additional areas or routes.
-
E.
openedAsSubway
Indicates that a transportation facility or line originally began operation specifically as a subway 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_69aed94564cc8190a9c1457daedb6e7f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefd0bdea48190805a79515ee92709 |
completed | March 9, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69aef90b2ef08190ae84febfd69dd48b |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:40 p.m.