Triple
T27428188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kawagoe Line |
E690549
|
entity |
| Predicate | doubleTrackingCompletedBetweenŌmiyaAndNisshin |
P162402
|
FINISHED |
| Object | 1985 |
—
|
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: 1985 | Statement: [Kawagoe Line, doubleTrackingCompletedBetweenŌmiyaAndNisshin, 1985]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doubleTrackingCompletedBetweenŌmiyaAndNisshin Context triple: [Kawagoe Line, doubleTrackingCompletedBetweenŌmiyaAndNisshin, 1985]
-
A.
distanceFromŌmiyaStation_km
Indicates the distance, measured in kilometers, between a given place and Ōmiya Station.
-
B.
distanceFromNagoyaCityCenterKilometers
Indicates the distance, measured in kilometers, between an entity and the center of Nagoya City.
-
C.
hasAdjacentStationOnShinetsuMainLine
Indicates that one station is directly next to another station along the Shinetsu Main Line.
-
D.
successorInServiceOnTokaido
Indicates that one entity took over or followed another in providing service on the Tokaido route or line.
-
E.
hasShinkansenStop
Indicates that a location is served by and includes a stop for a Shinkansen (high-speed rail) line.
- F. None of above. chosen
Provenance (4 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_69ef52003fb48190b0f1295246182a86 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f62d570d548190b7f696646baee862 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
| PDg | Predicate description generation | batch_69f624c006788190a2f4d5015c96463f |
completed | May 2, 2026, 4:22 p.m. |
Created at: April 27, 2026, 12:41 p.m.