Triple
T22566701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ainokaze Toyama Railway Line |
E557969
|
entity |
| Predicate | openingDateAsThirdSectorLine |
P148758
|
FINISHED |
| Object | 2015-03-14 |
—
|
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: 2015-03-14 | Statement: [Ainokaze Toyama Railway Line, openingDateAsThirdSectorLine, 2015-03-14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingDateAsThirdSectorLine Context triple: [Ainokaze Toyama Railway Line, openingDateAsThirdSectorLine, 2015-03-14]
-
A.
openingDateLineC
Indicates the calendar date on which entity C is opened, initiated, or begins operation.
-
B.
openingDateAsThroughLine
Indicates that the opening date is used as a continuous reference or organizing thread linking related events, records, or states over time.
-
C.
line3OpeningDate
Indicates the calendar date on which the third line (e.g., a route, service line, or similar system component) was officially opened or began operation.
-
D.
openingDate_Line2
Indicates the secondary or alternative date on which something (such as a facility, service, or event) is opened or becomes operational.
-
E.
openingDateLineA
Indicates the date on which Line A officially began operating or was opened.
- 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_69e11e5ae4ac8190b1f503457603d969 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15faaa0b081908d5aa8f3ba1e3dd3 |
completed | April 29, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69ee626e6bb08190ada4dd8b48cc0c43 |
completed | April 26, 2026, 7:07 p.m. |
| PDg | Predicate description generation | batch_69ee8841e9cc81908d23b34215e3be71 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 16, 2026, 8:52 p.m.