Triple
T37864729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 嵯峨野線 |
E944438
|
entity |
| Predicate | 地域輸送の役割 |
P6821
|
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.
transportationRole
chosen
Indicates a role or function that an entity has specifically in the context of providing, operating, or supporting transportation.
-
B.
primaryTransportFunction
Indicates the main mode or role by which something serves to move people, goods, or information from one place to another.
-
C.
transportRole
Indicates that an entity participates in a transportation process with a specific functional role (e.g., carrier, passenger, cargo, or operator).
-
D.
servesTransportCorridor
Indicates that something functions as a route or pathway facilitating the movement or transport of people, goods, or services between locations.
-
E.
transportedBetween
Indicates that an entity is moved or conveyed from one specified location or state to another.
- 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_69f76eee2f9c8190b1272aa2ee55ebf5 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbbae559a8819086ef839973f8d9b2 |
completed | May 6, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69fbb1440fa08190abf25ba684f75b6e |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.