Triple
T23642935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yangjae Station |
E583949
|
entity |
| Predicate | ShinbundangLineOpeningDate |
P10389
|
FINISHED |
| Object | 2011-10-29 |
—
|
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: 2011-10-29 | Statement: [Yangjae Station, ShinbundangLineOpeningDate, 2011-10-29]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ShinbundangLineOpeningDate Context triple: [Yangjae Station, ShinbundangLineOpeningDate, 2011-10-29]
-
A.
originalBundangLineOpening
Indicates that an event corresponds to the opening of the original Bundang Line.
-
B.
firstSubwayOpeningDate
Indicates the calendar date on which a subway system or line first began operating.
-
C.
openingDateToRapidTransit
Indicates the date on which a rapid transit service or connection was opened or became operational.
-
D.
metroLineInaugurated
chosen
Indicates that a metro line was officially opened and began operation on a specific date or during a specific event.
-
E.
TokyoMetroSectionOpeningDate
Indicates the calendar date on which a specific section of the Tokyo Metro railway network was officially opened for 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_69e248fefafc81909656921192f30e80 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b2821cb881909b1ab77aa77208e0 |
completed | April 29, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:48 p.m.