Triple
T37345195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hisaya-odori Station |
E927152
|
entity |
| Predicate | sakuradoriLineServiceStarted |
P187753
|
FINISHED |
| Object | 1989-09-10 |
—
|
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: 1989-09-10 | Statement: [Hisaya-odori Station, sakuradoriLineServiceStarted, 1989-09-10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sakuradoriLineServiceStarted Context triple: [Hisaya-odori Station, sakuradoriLineServiceStarted, 1989-09-10]
-
A.
tozaiLineServiceStart
Indicates the starting point or initiation of service on the Tozai Line.
-
B.
ShinkansenServiceStarted
Indicates that a Shinkansen (high-speed rail) service has commenced operation on a particular route or section.
-
C.
successorInServiceOnTokaido
Indicates that one entity took over or followed another in providing service on the Tokaido route or line.
-
D.
servedByLine
Indicates that a transportation stop, station, or location is provided service by a specific transit line.
-
E.
NorikuraSkylineStatus
Indicates the operational status or accessibility condition of the Norikura Skyline road at a given time.
- 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_69f76eb5e034819088e53ab5b7909a68 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb8c38a9688190be524246f5682107 |
completed | May 6, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9c6e0481908565bd849e869b24 |
completed | May 6, 2026, 3:13 p.m. |
| PDg | Predicate description generation | batch_69fb8c37931c81909da038c18ed9add2 |
completed | May 6, 2026, 6:45 p.m. |
Created at: May 3, 2026, 4:16 p.m.