Triple
T3812542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kyushu Shinkansen |
E93167
|
entity |
| Predicate | finalSectionOpeningDate |
P51995
|
FINISHED |
| Object | 2011-03-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: 2011-03-12 | Statement: [Kyushu Shinkansen, finalSectionOpeningDate, 2011-03-12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalSectionOpeningDate Context triple: [Kyushu Shinkansen, finalSectionOpeningDate, 2011-03-12]
-
A.
endDate
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
-
B.
finalAppTransitionDate
Indicates the date on which the final transition or change of state for the application was completed.
-
C.
finalShowDate
Indicates the date on which a show, series, or performance has its last scheduled or final airing or presentation.
-
D.
finalDeliveryDate
Indicates the date on which the last or ultimate delivery in a sequence of deliveries is scheduled or actually occurs.
-
E.
softOpeningDate
Indicates the date on which a business, venue, or service begins limited or trial operations before its official grand opening.
- 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_69aed96a60088190ab1df8390fffc935 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aef1515c688190a38332aedeed8a76 |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee7482d708190a3ec74745b102a4c |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aef14f9bb4819098e64b527b546d74 |
completed | March 9, 2026, 4:11 p.m. |
Created at: March 9, 2026, 3:16 p.m.