Triple
T25627477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rokujizō Station |
E642471
|
entity |
| Predicate | KeihanSectionOpeningDate |
P158937
|
FINISHED |
| Object | 1995-07-12 |
—
|
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: 1995-07-12 | Statement: [Rokujizō Station, KeihanSectionOpeningDate, 1995-07-12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: KeihanSectionOpeningDate Context triple: [Rokujizō Station, KeihanSectionOpeningDate, 1995-07-12]
-
A.
TokyoMetroSectionOpeningDate
Indicates the calendar date on which a specific section of the Tokyo Metro railway network was officially opened for service.
-
B.
TokyoMetroSection
Indicates a relationship where a specific segment or portion of the Tokyo Metro railway network is identified as a distinct section within the system.
-
C.
openingDateOnChiyodaLine
Indicates the date on which something (such as a station or facility) was opened on the Chiyoda Line.
-
D.
TokyoMetroStationNumber
Indicates that an entity is assigned a specific official station number within the Tokyo Metro railway network.
-
E.
FukutoshinLineOpeningDate
Indicates the calendar date on which the Fukutoshin Line officially began operation or was opened to the public.
- F. None of above. chosen
Provenance (4 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_69e77e7bd4548190a0c691b8a2f27ff1 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fa248b6c8190b79173bc9d806f21 |
completed | May 2, 2026, 1:20 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69f48b9058d081908ec9af261ee092e2 |
completed | May 1, 2026, 11:16 a.m. |
Created at: April 21, 2026, 5:15 p.m.