Triple

T29377224
Position Surface form Disambiguated ID Type / Status
Subject Linqing City E745032 entity
Predicate hasCanalFunction P194124 FINISHED
Object transshipment point on the Grand Canal 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: transshipment point on the Grand Canal | Statement: [Linqing City, hasCanalFunction, transshipment point on the Grand Canal]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCanalFunction
Context triple: [Linqing City, hasCanalFunction, transshipment point on the Grand Canal]
  • A. hasCanalOrChannel
    Indicates that one entity possesses, contains, or is traversed by a canal or channel that serves as a conduit or passageway.
  • B. hasCanalSection
    Indicates a relationship where one entity includes, contains, or is associated with a specific section or segment of a canal.
  • C. hasCanalDirection
    Indicates that a canal has a specific directional orientation or flow direction relative to a reference.
  • D. hasCanalParallel
    Indicates that one canal runs parallel to another canal without intersecting it.
  • E. hasCanalLock
    Indicates that one entity (typically a canal or waterway) includes or is equipped with a canal lock used to raise and lower boats between stretches of water at different levels.
  • 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_69f0a79cfd5481909b4dde750cb8d2c6 completed April 28, 2026, 12:27 p.m.
NER Named-entity recognition batch_69fd64bc86848190a49f451a8fc5cf1e completed May 8, 2026, 4:21 a.m.
PD Predicate disambiguation batch_69fd5ff4a648819090756d90fd195d9a completed May 8, 2026, 4 a.m.
PDg Predicate description generation batch_69fd64bb345c819096a35c72784a8ce3 completed May 8, 2026, 4:21 a.m.
Created at: April 28, 2026, 2:32 p.m.