Triple
T35909034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 0 series Shinkansen |
E1038553
|
entity |
| Predicate | alsoOperatedOnLine |
P15252
|
FINISHED |
| Object | Sanyo Shinkansen |
—
|
NE NERFINISHED |
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: Sanyo Shinkansen | Statement: [0 series Shinkansen, alsoOperatedOnLine, Sanyo Shinkansen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoOperatedOnLine Context triple: [0 series Shinkansen, alsoOperatedOnLine, Sanyo Shinkansen]
-
A.
operatesOnLine
chosen
Indicates that an entity conducts operations, services, or activities along a specific line or route.
-
B.
alsoOperatedBy
Indicates that an entity is additionally operated or managed by another operator, alongside any primary or other operators.
-
C.
alsoUsedOnLine
Indicates that something used in one context, medium, or location is additionally used on a specific line (such as a route, circuit, or sequence).
-
D.
operatedOnRailroad
Indicates that an entity conducted operations or provided services on a railroad system.
-
E.
operatedAmong
Indicates that an entity carried out operations or activities within, or in coordination with, a specified group, set, or collection of other entities.
- 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_69f76e2259608190bf6788a132e0d139 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa71a66c81909dba6a2c3466284c |
completed | May 3, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:07 p.m.