Triple
T9942907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akita Shinkansen |
E194126
|
entity |
| Predicate | introducedMiniShinkansenConcept |
P201
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Akita Shinkansen, introducedMiniShinkansenConcept, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedMiniShinkansenConcept Context triple: [Akita Shinkansen, introducedMiniShinkansenConcept, no]
-
A.
introducedByAmtrak
Indicates that something (such as a service, policy, feature, or change) was initiated, launched, or brought into use by Amtrak.
-
B.
introducedConcept
chosen
Indicates that one entity is responsible for presenting, defining, or bringing a new concept into use or awareness for another entity or context.
-
C.
SeikanTunnelConnects
Indicates that the Seikan Tunnel serves as a physical connection between two geographic locations or regions.
-
D.
introducedRollingStock
Indicates that an entity caused new rolling stock (such as trains or rail vehicles) to be put into service or use.
-
E.
introducedAsHighSpeedService
Indicates that a service was launched or presented specifically as a high-speed offering.
- 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_69ca82e409348190a393777356b80a2a |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb6124a188190b41feadb7b2f8922 |
completed | April 2, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9428cc81909b4b4938566d78a7 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:45 p.m.