Triple

T19633330
Position Surface form Disambiguated ID Type / Status
Subject Lock O-7 E471324 entity
Predicate hasName P744 FINISHED
Object Lock O-7 — 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: Lock O-7 | Statement: [Lock O-7, hasName, Lock O-7]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Lock O-7
Context triple: [Lock O-7, hasName, Lock O-7]
  • A. Lock O-7 chosen
    Lock O-7 is one of the navigation locks on New York State’s Oswego Canal, used to raise and lower boats between different water levels along the waterway.
  • B. Lock O-1
    Lock O-1 is a navigation lock on New York State’s Oswego Canal that helps vessels transition between different water levels along the waterway.
  • C. Lock O-8
    Lock O-8 is one of the numbered navigation locks on New York State’s Oswego Canal, used to raise and lower boats between different water levels along the waterway.
  • D. Lock O-2
    Lock O-2 is one of the navigation locks on New York State’s Oswego Canal, helping vessels transit between different water levels along the waterway.
  • E. Lock O-6
    Lock O-6 is one of the navigation locks on New York State’s Oswego Canal, used to raise and lower boats as they travel between the Erie Canal and Lake Ontario.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e511f28481909f4bc3ea9191e54a completed April 10, 2026, 11:54 a.m.
NER Named-entity recognition batch_69e6410449ec8190b8c20c0e09cd9156 completed April 20, 2026, 3:06 p.m.
Created at: April 10, 2026, 1:44 p.m.