Triple
T25417380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karasuma Oike Station |
E636875
|
entity |
| Predicate | tozaiLineServiceStart |
P158280
|
FINISHED |
| Object | 1997-10-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: 1997-10-12 | Statement: [Karasuma Oike Station, tozaiLineServiceStart, 1997-10-12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tozaiLineServiceStart Context triple: [Karasuma Oike Station, tozaiLineServiceStart, 1997-10-12]
-
A.
ShinkansenServiceStarted
Indicates that a Shinkansen (high-speed rail) service has commenced operation on a particular route or section.
-
B.
successorInServiceOnTokaido
Indicates that one entity took over or followed another in providing service on the Tokaido route or line.
-
C.
operatesShinkansenSection
Indicates that an entity operates or manages the service of a specific section of a Shinkansen (high-speed rail) line.
-
D.
operatesServiceTo
Indicates that one entity runs or provides a transportation or service route to another entity or location.
-
E.
blueLineServiceBegan
Indicates that service on the Blue Line began operating at a specified time or event.
- 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_69e75db4135881909acc287ebcb7a505 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5b013596c81909af7acebfc72bfc6 |
completed | May 2, 2026, 8:04 a.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
| PDg | Predicate description generation | batch_69f464ae42e88190b3549fdf4e0b425e |
completed | May 1, 2026, 8:30 a.m. |
Created at: April 21, 2026, 1:55 p.m.