Triple

T7500504
Position Surface form Disambiguated ID Type / Status
Subject Küsten Canal E177244 entity
Predicate connectsRiverSystem P48420 FINISHED
Object Ems river system 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: Ems river system | Statement: [Küsten Canal, connectsRiverSystem, Ems river system]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: connectsRiverSystem
Context triple: [Küsten Canal, connectsRiverSystem, Ems river system]
  • A. waterwayLinkBetween chosen
    Indicates a connection or linkage between two waterways, such as rivers, canals, or channels, through which water can flow or navigation can occur.
  • B. connectsCityToRiver
    Indicates a relationship where a city is linked or joined to a river, typically via infrastructure such as roads, bridges, or transport routes.
  • C. riverSystem
    Indicates that one entity is a river system to which the other entity belongs or is a component (such as a tributary or segment).
  • D. waterwaySystem
    Indicates that one entity is part of, or belongs to, a connected network of waterways associated with another entity.
  • E. tributarySystem
    Indicates a relationship where one political entity pays regular tribute or offers deference to another, acknowledging the latter’s superior authority or status.
  • 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_69c69f2696688190915a8458f2398211 completed March 27, 2026, 3:15 p.m.
NER Named-entity recognition batch_69c6f81b431481908214b69c6c8d83bc completed March 27, 2026, 9:35 p.m.
PD Predicate disambiguation batch_69c6f4d266d88190982cf5d2ee2e9564 completed March 27, 2026, 9:21 p.m.
Created at: March 27, 2026, 3:44 p.m.