Triple
T11406015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JNR |
E270239
|
entity |
| Predicate | operatedHighSpeedService |
P35275
|
FINISHED |
| Object | Shinkansen network |
—
|
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: Shinkansen network | Statement: [JNR, operatedHighSpeedService, Shinkansen network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedHighSpeedService Context triple: [JNR, operatedHighSpeedService, Shinkansen network]
-
A.
introducedAsHighSpeedService
Indicates that a service was launched or presented specifically as a high-speed offering.
-
B.
operatesInterCityServices
Indicates that an entity runs or provides transportation services connecting different cities.
-
C.
hasHighSpeedLine
Indicates that there exists a high-speed rail line connection between the related entities.
-
D.
primaryHighSpeedOperator
chosen
Indicates that an entity serves as the main operator responsible for providing high-speed service or functionality to another entity.
-
E.
operatedPassengerServices
Indicates that an entity provided and managed transportation services specifically for carrying passengers.
- 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_69d6aaddeaa8819088b30ef7b50598c9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8014c820c81908538ba4a08e13230 |
completed | April 9, 2026, 7:43 p.m. |
| PD | Predicate disambiguation | batch_69d7e70ffd708190b62a78ebcbce9f78 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:34 p.m.