Triple
T36020971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 京浜東北線 |
E1041981
|
entity |
| Predicate | 並行路線 |
P19597
|
FINISHED |
| Object | 東海道本線 |
—
|
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: 東海道本線 | Statement: [京浜東北線, 並行路線, 東海道本線]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 並行路線 Context triple: [京浜東北線, 並行路線, 東海道本線]
-
A.
parallelRoute
chosen
Indicates that one route runs alongside and in the same general direction as another route without intersecting it.
-
B.
parallelTransportCorridor
Indicates a relationship where one path, route, or connection is used to transport something in a way that preserves its structure or configuration relative to another, typically along a shared or corresponding trajectory.
-
C.
operatedAlongside
Indicates that two or more entities functioned or were active together in a coordinated or concurrent manner within the same context or system.
-
D.
hasParallelStreet
Indicates that one street runs parallel to another street, maintaining a constant distance without intersecting.
-
E.
isOfficialRoute
Indicates that a given path, course, or connection is formally recognized and designated as an authorized route.
- 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_69f76e2b981881908e4e160607fa82eb |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ace302e08190a7ea85706d581063 |
completed | May 3, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69f7ab75387c819091afc3c2128eb903 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.