Triple

T19746856
Position Surface form Disambiguated ID Type / Status
Subject Dry Fork E474273 entity
Predicate flowsInto P408 FINISHED
Object Black Fork 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: Black Fork | Statement: [Dry Fork, flowsInto, Black Fork]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Black Fork
Context triple: [Dry Fork, flowsInto, Black Fork]
  • A. Black Fork chosen
    Black Fork is a tributary stream that forms one of the principal headwaters of the Cheat River in the Appalachian region of West Virginia.
  • B. Blacks Fork
    Blacks Fork is a river in southwestern Wyoming and northeastern Utah that serves as a significant tributary of the Green River within the Colorado River watershed.
  • C. Glady Fork
    Glady Fork is a scenic mountain stream in eastern West Virginia known for its trout fishing and role in forming part of the Cheat River watershed.
  • D. Baron Fork
    Baron Fork is a tributary stream in eastern Oklahoma that flows through the Cookson Hills before joining the Illinois River.
  • E. Shavers Fork
    Shavers Fork is a major headwater stream of the Cheat River in West Virginia, known for its scenic mountain setting and trout fishing opportunities.
  • 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_69d8e51940a0819087bd2996f98da668 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e65294b4008190818eda40630f4147 completed April 20, 2026, 4:21 p.m.
Created at: April 10, 2026, 1:47 p.m.