Triple

T15077911
Position Surface form Disambiguated ID Type / Status
Subject Stony River E380053 entity
Predicate hasName P744 FINISHED
Object Stony River 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: Stony River | Statement: [Stony River, hasName, Stony River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Stony River
Context triple: [Stony River, hasName, Stony River]
  • A. Stony River chosen
    Stony River is a tributary waterway in Alaska that feeds into the Kuskokwim River system.
  • B. Stony River
    Stony River is a river in West Virginia that serves as the primary inflow and outflow for Mount Storm Lake, a reservoir used for power generation and recreation.
  • C. Stoney River
    Stoney River is a watercourse in Ireland that serves as one of the tributary rivers feeding into Lough Allen in the River Shannon system.
  • D. Raisin River
    The Raisin River is a waterway in eastern Ontario, Canada, known for flowing through rural communities such as South Glengarry before emptying into the St. Lawrence River.
  • E. Raisin River
    The Raisin River is a river in southeastern Michigan that flows through the Lower Peninsula into Lake Erie, historically notable for its role in the War of 1812.
  • 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_69d85cd7683881908d405c1b5d7b4f7f completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69dff7fe5a208190823900b25e298dab completed April 15, 2026, 8:41 p.m.
Created at: April 10, 2026, 3:03 a.m.