Triple

T19062591
Position Surface form Disambiguated ID Type / Status
Subject Lock CS30 E466570 entity
Predicate hasAlternativeName P39 FINISHED
Object CS30 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: CS30 Lock | Statement: [Lock CS30, hasAlternativeName, CS30 Lock]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: CS30 Lock
Context triple: [Lock CS30, hasAlternativeName, CS30 Lock]
  • A. Lock CS32
    Lock CS32 is a navigation lock on New York State’s Cayuga–Seneca Canal that helps vessels transition between different water levels along the waterway.
  • B. Lock CS30 chosen
    Lock CS30 is a navigation lock on New York State’s Cayuga–Seneca Canal that helps vessels transition between different water levels along the canal system.
  • C. Lock CS31
    Lock CS31 is a navigation lock on New York State’s Cayuga–Seneca Canal that helps vessels transition between different water levels along the canal.
  • D. Lock CS33
    Lock CS33 is one of the navigation locks on New York State’s Cayuga–Seneca Canal, used to raise and lower boats between different water levels along the waterway.
  • E. Lock CS3
    Lock CS3 is a navigation lock on New York State’s Cayuga–Seneca Canal that helps vessels transition between different water levels along the waterway.
  • 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_69d8dd040fb881909af2a964f65ad208 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5e195ac048190a57b57e585d022d4 completed April 20, 2026, 8:19 a.m.
Created at: April 10, 2026, 12:03 p.m.