Triple
T17733413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kokkai-gijidō-mae Station |
E442644
|
entity |
| Predicate | openingDateOnChiyodaLine |
P128796
|
FINISHED |
| Object | 1972 |
—
|
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: 1972 | Statement: [Kokkai-gijidō-mae Station, openingDateOnChiyodaLine, 1972]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingDateOnChiyodaLine Context triple: [Kokkai-gijidō-mae Station, openingDateOnChiyodaLine, 1972]
-
A.
TokyoMetroSectionOpeningDate
Indicates the calendar date on which a specific section of the Tokyo Metro railway network was officially opened for service.
-
B.
FukutoshinLineOpeningDate
Indicates the calendar date on which the Fukutoshin Line officially began operation or was opened to the public.
-
C.
line2OpeningDate
Indicates the date on which the second line (e.g., a route, service, or facility line) was officially opened or began operation.
-
D.
openingDateToRapidTransit
Indicates the date on which a rapid transit service or connection was opened or became operational.
-
E.
openingDateToStreetcars
Indicates the date on which streetcar service began operating on or serving a particular location or route.
- 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_69d8b9ed3a2081909b2ec0d4dd2f4c37 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e478e86f188190a5dd7fb32fd04c7b |
completed | April 19, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69e3cde815e08190881972e2d80d151e |
completed | April 18, 2026, 6:31 p.m. |
| PDg | Predicate description generation | batch_69e3d37ab6988190bd326ea6f8dd4aaa |
completed | April 18, 2026, 6:54 p.m. |
Created at: April 10, 2026, 10:08 a.m.