Triple

T12093008
Position Surface form Disambiguated ID Type / Status
Subject Henry’s Fork E287993 entity
Predicate flowsThrough P225 FINISHED
Object Rexburg, Idaho E313063 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: Rexburg, Idaho | Statement: [Henry’s Fork, flowsThrough, Rexburg, Idaho]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rexburg, Idaho
Context triple: [Henry’s Fork, flowsThrough, Rexburg, Idaho]
  • A. Rexburg, Idaho chosen
    Rexburg, Idaho is a small city in eastern Idaho known for housing Brigham Young University–Idaho and serving as a regional educational and agricultural center.
  • B. Pocatello
    Pocatello is a city in southeastern Idaho known as a regional hub for education, commerce, and transportation.
  • C. Farmington, Idaho
    Farmington, Idaho is a small unincorporated rural community located in Latah County in the northern part of the state.
  • D. Meridian, Idaho
    Meridian, Idaho is a rapidly growing suburban city in the Boise metropolitan area known for its family-friendly neighborhoods, schools, and parks.
  • E. Lewiston, Idaho
    Lewiston, Idaho is a small city in north-central Idaho known as a key port on the Snake River and a regional hub for the Inland Northwest.
  • 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_69d6ab4964708190850585628b287b0c completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d91550ce508190babf5755e1553734 completed April 10, 2026, 3:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69f62a7e1ab481909c25ba3dd3fff9b3 completed May 2, 2026, 4:46 p.m.
Created at: April 8, 2026, 9:48 p.m.