Triple
T35909017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 0 series Shinkansen |
E1038553
|
entity |
| Predicate | finalRegularService |
P176633
|
FINISHED |
| Object | 30 November 2008 |
—
|
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: 30 November 2008 | Statement: [0 series Shinkansen, finalRegularService, 30 November 2008]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalRegularService Context triple: [0 series Shinkansen, finalRegularService, 30 November 2008]
-
A.
finalService
Indicates that a service represents the last or concluding service in a sequence, process, or lifecycle.
-
B.
finalUsuallyOn
Indicates that an event or process typically concludes or reaches its final state on a particular time, date, or condition.
-
C.
plannedService
Indicates that a service is scheduled or intended to be provided, but has not yet occurred.
-
D.
closureDateForRegularService
chosen
Indicates the date on which a regular, ongoing service is formally closed or terminated.
-
E.
afterService
Indicates that one event, action, or state occurs subsequent to the completion of a specified 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_69f76e2259608190bf6788a132e0d139 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69feba0f09508190b3e871c62b19ec7f |
completed | May 9, 2026, 4:37 a.m. |
| PD | Predicate disambiguation | batch_69feb957fe7c8190969fb31a6d1a59c8 |
completed | May 9, 2026, 4:34 a.m. |
Created at: May 3, 2026, 4:07 p.m.