Triple
T35485471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Odenplan |
E1025583
|
entity |
| Predicate | openingDateOfCommuterRailStation |
P14462
|
FINISHED |
| Object | 2017-07-10 |
—
|
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: 2017-07-10 | Statement: [Odenplan, openingDateOfCommuterRailStation, 2017-07-10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingDateOfCommuterRailStation Context triple: [Odenplan, openingDateOfCommuterRailStation, 2017-07-10]
-
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.
openingDateToRapidTransit
Indicates the date on which a rapid transit service or connection was opened or became operational.
-
C.
openingDateOfTramTerminus
Indicates the date on which a tram terminus was officially opened for service.
-
D.
railwaySectionOpeningDate
Indicates the date on which a specific section of a railway line was officially opened for operation.
-
E.
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).
- 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_69f76dfbcdd881908c7b0b6bc502252b |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: May 3, 2026, 4:04 p.m.