Triple

T36721037
Position Surface form Disambiguated ID Type / Status
Subject Crooked River (Michigan) E907059 entity
Predicate hasLockOrDam P85577 FINISHED
Object Crooked River Lock NE NERFINISHED

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: Crooked River Lock | Statement: [Crooked River (Michigan), hasLockOrDam, Crooked River Lock]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLockOrDam
Context triple: [Crooked River (Michigan), hasLockOrDam, Crooked River Lock]
  • A. hasLockAndDamSystem
    Indicates that one entity possesses or is equipped with a system of locks and dams used to control water levels and facilitate navigation.
  • B. hasDownstreamDam
    Indicates that one water barrier or dam is located downstream from another along the same watercourse.
  • C. isUndammed
    Indicates that a watercourse or river segment is free of dams or artificial barriers that obstruct its natural flow.
  • D. hasCanalLock chosen
    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.
  • E. hasMajorDams
    Indicates that the subject possesses or contains one or more significant dams, typically large or important water-retaining structures.
  • 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_69f76e746e4c8190a0d05cc6d57a643e completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69ff6ef0d61c81909162d37c15a1a3c3 completed May 9, 2026, 5:29 p.m.
PD Predicate disambiguation batch_69ff6c6a58e08190921317062cd9d489 completed May 9, 2026, 5:18 p.m.
Created at: May 3, 2026, 4:12 p.m.