Triple

T17860101
Position Surface form Disambiguated ID Type / Status
Subject Quinebaug River E446047 entity
Predicate hasTributary P415 FINISHED
Object Mashamoquet Brook 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: Mashamoquet Brook | Statement: [Quinebaug River, hasTributary, Mashamoquet Brook]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mashamoquet Brook
Context triple: [Quinebaug River, hasTributary, Mashamoquet Brook]
  • A. Mashamoquet Brook chosen
    Mashamoquet Brook is a small watercourse in northeastern Connecticut known for flowing through and giving its name to Mashamoquet Brook State Park.
  • B. Comstock Brook
    Comstock Brook is a small stream in southwestern Connecticut that serves as a tributary feeding into the Norwalk River.
  • C. Beaver Brook
    Beaver Brook is a smaller stream in New Jersey that feeds into the Musconetcong River as part of the region’s freshwater watershed.
  • D. Beaver Brook
    Beaver Brook is a stream in the town of Dracut, Massachusetts, that forms part of the local watershed and natural landscape.
  • E. Beaver Brook
    Beaver Brook is a stream in southern New Hampshire that flows through the town of Pelham and surrounding communities.
  • 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_69d8b9f26f18819089c9e43250bee6ae completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e4978f34948190a25deb4fd617ad72 completed April 19, 2026, 8:51 a.m.
Created at: April 10, 2026, 10:17 a.m.