Triple
T28217332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsurugi |
E711347
|
entity |
| Predicate | serviceStartEvent |
P143780
|
FINISHED |
| Object | opening of the Hokuriku Shinkansen extension from Nagano to Kanazawa |
—
|
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: opening of the Hokuriku Shinkansen extension from Nagano to Kanazawa | Statement: [Tsurugi, serviceStartEvent, opening of the Hokuriku Shinkansen extension from Nagano to Kanazawa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceStartEvent Context triple: [Tsurugi, serviceStartEvent, opening of the Hokuriku Shinkansen extension from Nagano to Kanazawa]
-
A.
serviceStartContext
Indicates the circumstances or conditions under which a service begins or is initiated.
-
B.
serviceStartLocation
Indicates the place where a service or operation is initiated or begins.
-
C.
serviceResumed
Indicates that a previously interrupted or suspended service has been restarted and is functioning again.
-
D.
operationStart
Indicates the point in time or event at which a specific operation or process begins.
-
E.
throughServiceStarted
chosen
Indicates that a through (direct, continuing) service between locations has begun operation.
- 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_69efb51cb5288190818c1f63a266af11 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 27, 2026, 10:44 p.m.