Triple

T12780237
Position Surface form Disambiguated ID Type / Status
Subject Hackensack River E305486 entity
Predicate hasTributary P415 FINISHED
Object Overpeck Creek 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: Overpeck Creek | Statement: [Hackensack River, hasTributary, Overpeck Creek]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Overpeck Creek
Context triple: [Hackensack River, hasTributary, Overpeck Creek]
  • A. Overpeck Creek chosen
    Overpeck Creek is a tributary stream in northeastern New Jersey that flows through Bergen County into the Hackensack River, bordered by wetlands, parks, and urban communities.
  • B. Well Creek
    Well Creek is a waterway associated with the locality of Upwell in England, forming part of the region’s drainage and navigation network.
  • C. Wahoo Creek
    Wahoo Creek is a stream in eastern Nebraska that lends its name to the nearby city of Wahoo.
  • D. Tinemaha Creek
    Tinemaha Creek is a stream in eastern California that feeds into the Owens River, contributing to the hydrology of the Owens Valley region.
  • E. Assunpink Creek
    Assunpink Creek is a stream in central New Jersey historically notable as the site of a pivotal American Revolutionary War engagement during the Trenton campaign.
  • 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_69d7bdf2b43c819098ae5aa68e61ea58 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d96e5a5680819095dcd491486d23e7 completed April 10, 2026, 9:40 p.m.
Created at: April 9, 2026, 5:29 p.m.