Triple
T21164780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shinano Railway Line |
E521529
|
entity |
| Predicate | isKeyLocalCorridor |
P121975
|
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: [Shinano Railway Line, isKeyLocalCorridor, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isKeyLocalCorridor Context triple: [Shinano Railway Line, isKeyLocalCorridor, true]
-
A.
isStopOnCorridor
Indicates that a location functions as a designated stop situated along a corridor or route.
-
B.
onCorridorBetween
Indicates that one entity is located along the corridor that lies between two other reference entities or areas.
-
C.
isPartOfCorridorSystem
Indicates that one entity forms a component or segment within a larger interconnected corridor system.
-
D.
hasCorridor
Indicates that one entity includes, is connected by, or provides access through a corridor to another entity.
-
E.
isStrategicCorridor
chosen
Indicates that a route, passage, or area serves as a critical pathway for movement, access, or control, giving it significant strategic importance.
- 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_69e0b50e30748190b186824a206d39b9 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7270e15bc81908d609198e573040e |
completed | April 21, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69e5f5f8a5bc819081918c7fa8e4496d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:59 p.m.