Triple
T21715709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SSライン |
E536022
|
entity |
| Predicate | 関連路線 |
P848
|
FINISHED |
| Object | 東海道本線 |
—
|
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: 東海道本線 | Statement: [SSライン, 関連路線, 東海道本線]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 関連路線 Context triple: [SSライン, 関連路線, 東海道本線]
-
A.
isRelatedRouteOf
Indicates that one route is connected to, associated with, or serves as an alternative or complementary path to another route.
-
B.
associatedLine
Indicates that one entity is linked or connected to a particular line (such as a line item, line of text, or line in a structure) with which it is contextually or functionally related.
-
C.
relatedRailroad
Indicates that there is an association or connection between an entity and a specific railroad, such as ownership, operation, service, or historical linkage.
-
D.
railwayLine
chosen
Indicates that there is a railway line connection or route associated with or passing through the referenced entity.
-
E.
associatedWithTransitLine
Indicates that an entity has a connection or linkage to a specific transit line, such as being part of, served by, or otherwise related to that line.
- 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_69e0c46c6dd88190a595375fa6ebd701 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efb53761b48190954a46e8155a84f0 |
completed | April 27, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69e6969725bc81908e7ad19619ba2688 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:47 p.m.