Triple
T20708069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finse |
E508955
|
entity |
| Predicate | hasRailwayStationOpeningYear |
P14462
|
FINISHED |
| Object | 1908 |
—
|
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: 1908 | Statement: [Finse, hasRailwayStationOpeningYear, 1908]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRailwayStationOpeningYear Context triple: [Finse, hasRailwayStationOpeningYear, 1908]
-
A.
railwayStationOpened
chosen
Indicates that a railway station began operation or was officially opened on a specified date or in a specified time period.
-
B.
railwaySectionOpeningDate
Indicates the date on which a specific section of a railway line was officially opened for operation.
-
C.
railwayOpenedWith
Indicates that a railway line or section was inaugurated and began operation together with a specified associated element (such as a station, segment, or service).
-
D.
reopenedRailwayStationYear
Indicates the year in which a previously closed railway station was reopened to service.
-
E.
railTunnelOpeningYear
Indicates the calendar year in which a rail tunnel was officially opened for use.
- 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_69e0b4c40ad88190b81f77695366d328 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1952e888190877b79933970f7b0 |
completed | April 21, 2026, 12:15 a.m. |
| PD | Predicate disambiguation | batch_69e5c044d1108190b2b5d25de23f6401 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:14 p.m.