Triple
T13037572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 京阪交野線 |
E326602
|
entity |
| Predicate | 路線種別 |
P14639
|
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: [京阪交野線, 路線種別, 普通鉄道]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 路線種別 Context triple: [京阪交野線, 路線種別, 普通鉄道]
-
A.
railwayLineType
chosen
Indicates the specific kind or classification of a railway line associated with an entity (e.g., main line, branch line, high-speed line).
-
B.
hasRailRoute
Indicates that there exists a rail-based transportation route or connection between the related entities.
-
C.
railServiceType
Indicates the specific category or type of rail service that applies to the relationship between the involved entities (e.g., local, express, freight).
-
D.
railwayLine
Indicates that there is a railway line connection or route associated with or passing through the referenced entity.
-
E.
railSystemType
Indicates the specific category or classification of a rail transportation system that an entity belongs to or operates within.
- 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_69d8076cc45c81908123123f43e69266 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d98a9829b48190b23624b6b3df4600 |
completed | April 10, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69d9803aca4c8190b1015cd159cc47a9 |
completed | April 10, 2026, 10:56 p.m. |
Created at: April 9, 2026, 8:55 p.m.