Triple

T22654501
Position Surface form Disambiguated ID Type / Status
Subject Bone on Bone E559186 entity
Predicate track P17929 FINISHED
Object False 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: False River | Statement: [Bone on Bone, track, False River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: False River
Context triple: [Bone on Bone, track, False River]
  • A. False River
    False River is a river in northern Quebec, Canada, that flows into Ungava Bay in the Arctic region.
  • B. False River
    False River is a tidal channel and backwater of the Sacramento–San Joaquin River Delta in Northern California, known for its fishing, boating, and wetland habitat.
  • C. False River chosen
    False River is an oxbow lake in southeastern Louisiana known for its recreational fishing, boating, and lakeside camps and homes.
  • D. Drift River
    Drift River is a river in Alaska that flows into Cook Inlet, known for its proximity to the Redoubt Volcano and associated lahar and flooding hazards.
  • E. Fiagdon River
    The Fiagdon River is a mountain river in the Caucasus region of Ossetia, known for flowing through scenic gorges and valleys.
  • 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_69e245489dd88190b1f674acf61c8769 completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f1765a97ac819095f21ccbdada1d0a completed April 29, 2026, 3:09 a.m.
Created at: April 17, 2026, 3:06 p.m.