Triple
T9916967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tōhoku Shinkansen |
E185892
|
entity |
| Predicate | isHighSpeedRail |
P48478
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Tōhoku Shinkansen, isHighSpeedRail, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHighSpeedRail Context triple: [Tōhoku Shinkansen, isHighSpeedRail, true]
-
A.
hasHighSpeedLine
chosen
Indicates that there exists a high-speed rail line connection between the related entities.
-
B.
hasHighSpeedRailStation
Indicates that a location is served by a high-speed rail station where high-speed trains regularly stop.
-
C.
hasHighSpeedRailProposal
Indicates that there exists a proposed plan or project to develop or implement a high-speed rail system involving the related entities.
-
D.
isBusiestPassengerRailLineIn
Indicates that a passenger rail line is the one with the highest level of use or traffic within a specified geographic area or system.
-
E.
hasRailSystem
Indicates that an entity possesses or is served by a rail-based transportation system.
- 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_69ca829b45f481909040f7b99a1976ed |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cdb540195881908f25f7dde5c66a75 |
completed | April 2, 2026, 12:16 a.m. |
| PD | Predicate disambiguation | batch_69cd1d90b8a8819081748f129c0c6ab6 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:42 p.m.