Triple
T34873991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokyo–Okayama |
E1005826
|
entity |
| Predicate | openedInStagesWith |
P40024
|
FINISHED |
| Object | Tōkaidō Shinkansen |
—
|
NE NERFINISHED |
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: Tōkaidō Shinkansen | Statement: [Tokyo–Okayama, openedInStagesWith, Tōkaidō Shinkansen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedInStagesWith Context triple: [Tokyo–Okayama, openedInStagesWith, Tōkaidō Shinkansen]
-
A.
openedInStages
Indicates that the opening or launch of something occurred in multiple distinct phases or stages rather than all at once.
-
B.
openedIn
Indicates that an entity (such as a business, event, or institution) began operating or was inaugurated in a specific time period or location.
-
C.
openedInPart
Indicates that an entity was opened or made accessible only partially, rather than fully or completely.
-
D.
openedDuring
Indicates that an entity began operating, became accessible, or was inaugurated within a specified time period or event.
-
E.
openedInSections
chosen
Indicates that something has been opened or made accessible in multiple distinct sections or parts.
- 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_69f76dbde1c08190a24e7f9beb564c8d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: May 3, 2026, 4 p.m.