Triple
T8089740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hokuriku Shinkansen |
E188825
|
entity |
| Predicate | sectionOpened |
P80433
|
FINISHED |
| Object | Tokyo–Nagano section opened 1997-10-01 |
—
|
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: Tokyo–Nagano section opened 1997-10-01 | Statement: [Hokuriku Shinkansen, sectionOpened, Tokyo–Nagano section opened 1997-10-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sectionOpened Context triple: [Hokuriku Shinkansen, sectionOpened, Tokyo–Nagano section opened 1997-10-01]
-
A.
openedWithSection
Indicates that something (such as a document, file, or resource) is opened starting from or via a specific section.
-
B.
openedSectionBetween
Indicates that one entity has created or established an open section, gap, or interval between itself and another entity.
-
C.
openedInSections
Indicates that something has been opened or made accessible in multiple distinct sections or parts.
-
D.
sectionCreated
Indicates that a new section has been created or added within a larger structure, document, or system.
-
E.
firstSectionOpened
Indicates that the initial section in a sequence or structure has been opened or activated.
- 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_69ca82b7b3e88190b9041ab0ef28b3cb |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb421e30e88190b9699b338b69b81c |
completed | March 31, 2026, 3:40 a.m. |
| PD | Predicate disambiguation | batch_69cb04a14cd88190a79ed26cbeec1c33 |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14be17208190bb51c3dfcb613f20 |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:29 p.m.