Triple

T19442655
Position Surface form Disambiguated ID Type / Status
Subject Bad Axe River area E486388 entity
Predicate mouthOfNearbyRiver P15504 FINISHED
Object confluence of Bad Axe River and Mississippi River 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: confluence of Bad Axe River and Mississippi River | Statement: [Bad Axe River area, mouthOfNearbyRiver, confluence of Bad Axe River and Mississippi River]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mouthOfNearbyRiver
Context triple: [Bad Axe River area, mouthOfNearbyRiver, confluence of Bad Axe River and Mississippi River]
  • A. closelyAssociatedRiver chosen
    Indicates a river that is geographically or functionally closely connected to the subject, such as flowing nearby, through, or otherwise strongly linked to it.
  • B. locatedOnTributaryOf
    Indicates that one entity is situated along or on the banks of a tributary that flows into another specified water body.
  • C. hasRiver
    Indicates that a location or area contains, is traversed by, or is directly associated with a river.
  • D. nearbyWatercourse
    Indicates that one entity is located close to or alongside a natural or artificial watercourse, such as a river, stream, or canal.
  • E. hasNearbyRiverStructure
    Indicates that a river-related structure (such as a dam, bridge, or levee) is located close to the referenced entity.
  • 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_69d8e8d7ad488190a3373045029b0f3b completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e63386c520819092bea5d7f259a226 completed April 20, 2026, 2:09 p.m.
PD Predicate disambiguation batch_69e4fd6e806081909053f325ba01ab6b completed April 19, 2026, 4:06 p.m.
Created at: April 10, 2026, 1:38 p.m.