Triple
T11143064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yurakucho Station |
E263602
|
entity |
| Predicate | JRSectionOpeningDate |
P68956
|
FINISHED |
| Object | 1910 |
—
|
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: 1910 | Statement: [Yurakucho Station, JRSectionOpeningDate, 1910]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: JRSectionOpeningDate Context triple: [Yurakucho Station, JRSectionOpeningDate, 1910]
-
A.
railwaySectionOpeningDate
chosen
Indicates the date on which a specific section of a railway line was officially opened for operation.
-
B.
railwayLineOpened
Indicates that a railway line began official operation or service on a specified date.
-
C.
railTunnelOpeningYear
Indicates the calendar year in which a rail tunnel was officially opened for use.
-
D.
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).
-
E.
railwayWorksOpened
Indicates that a railway facility, such as a station, line, or related infrastructure, was officially opened or began operation 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_69d6aa9c0ba08190bbd19c217489b755 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8623158819096ad1678fa9e72bb |
completed | April 9, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69d75ce104908190b6cc31ef2f67846a |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:28 p.m.