Triple

T2843581
Position Surface form Disambiguated ID Type / Status
Subject Battle of Assunpink Creek E62528 entity
Predicate river P165 FINISHED
Object Assunpink Creek E525305 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: Assunpink Creek | Statement: [Battle of Assunpink Creek, river, Assunpink Creek]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Assunpink Creek
Context triple: [Battle of Assunpink Creek, river, Assunpink Creek]
  • A. Assunpink Creek chosen
    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.
  • B. Hannibal Creek
    Hannibal Creek is a waterway after which the city of Hannibal, Missouri, is named.
  • C. Hunting Creek
    Hunting Creek is a smaller stream in North Carolina that feeds into the Yadkin River as one of its tributaries.
  • D. Cascadilla Creek
    Cascadilla Creek is a small stream in Ithaca, New York, that flows through the scenic Cascadilla Gorge with numerous waterfalls and cascades before emptying into Cayuga Lake.
  • E. Tulpehocken Creek
    Tulpehocken Creek is a significant waterway in southeastern Pennsylvania known for its historical role in transportation and its popular trout fishing and recreational opportunities.
  • 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_69ab4c3d16bc81908b3a1c98fbd287fe completed March 6, 2026, 9:50 p.m.
NER Named-entity recognition batch_69abdf1a07508190be35fe85733ddeed completed March 7, 2026, 8:17 a.m.
NED1 Entity disambiguation (via context triple) batch_69bf8bb93044819094d61035355c08f0 completed March 22, 2026, 6:27 a.m.
Created at: March 6, 2026, 10:02 p.m.