Triple

T3088731
Position Surface form Disambiguated ID Type / Status
Subject Hannibal, Missouri E64436 entity
Predicate namedAfter P63 FINISHED
Object Hannibal Creek E64436 NE FINISHED

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: Hannibal Creek | Statement: [Hannibal, Missouri, namedAfter, Hannibal Creek]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hannibal Creek
Context triple: [Hannibal, Missouri, namedAfter, Hannibal Creek]
  • A. Hannibal Creek chosen
    Hannibal Creek is a waterway after which the city of Hannibal, Missouri, is named.
  • B. 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.
  • C. Jamison Creek
    Jamison Creek is a small mountain stream in the Blue Mountains region of New South Wales, Australia, that flows through bushland and feeds the waterfalls and valleys around Wentworth Falls.
  • D. Sandburg Creek
    Sandburg Creek is a small stream in New York’s Hudson Valley that feeds into the larger Rondout Creek within the Catskill 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 (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_69ad857c97d88190b26f9b1c90839c77 completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69ada20b99a4819090c3d3e08ed556ad completed March 8, 2026, 4:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69bfe8ba08f88190a0b10b7a0a05b98c completed March 22, 2026, 1:03 p.m.
Created at: March 8, 2026, 3:03 p.m.