Triple

T34036579
Position Surface form Disambiguated ID Type / Status
Subject Keihan network between Osaka and Kyoto E872813 entity
Predicate connectsRiverCorridor P199581 FINISHED
Object Yodo River corridor 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: Yodo River corridor | Statement: [Keihan network between Osaka and Kyoto, connectsRiverCorridor, Yodo River corridor]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: connectsRiverCorridor
Context triple: [Keihan network between Osaka and Kyoto, connectsRiverCorridor, Yodo River corridor]
  • A. connectsRiverValley
    Indicates a relationship where something links or spans between a river and a valley, serving as a connection between the two.
  • B. linkedToRiver
    Indicates a relationship where something is physically or functionally connected to, associated with, or dependent on a river.
  • C. connectsCityToRiver
    Indicates a relationship where a city is linked or joined to a river, typically via infrastructure such as roads, bridges, or transport routes.
  • D. useRiverSystems
    Indicates that an entity utilizes or manages river systems for a particular purpose or function.
  • E. waterwayLinkBetween
    Indicates a connection or linkage between two waterways, such as rivers, canals, or channels, through which water can flow or navigation can occur.
  • F. None of above. chosen

Provenance (4 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_69f349a3363081909cea4c9a848cefe2 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69ff46afe7e481908f2862ed11c88db2 completed May 9, 2026, 2:37 p.m.
PD Predicate disambiguation batch_69ff45e9151881909c444a655e852165 completed May 9, 2026, 2:34 p.m.
PDg Predicate description generation batch_69ff46aefe248190a80d898df6ef1340 completed May 9, 2026, 2:37 p.m.
Created at: May 1, 2026, 1:51 a.m.