Triple

T24018975
Position Surface form Disambiguated ID Type / Status
Subject Cheat River basin E594763 entity
Predicate contains P35 FINISHED
Object Deckers Creek
Deckers Creek is a tributary stream in north-central West Virginia known for flowing through Monongalia and Preston counties before joining the Monongahela River at Morgantown.
E1628932 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: Deckers Creek | Statement: [Cheat River basin, contains, Deckers Creek]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Deckers Creek
Triple: [Cheat River basin, contains, Deckers Creek]
Generated description
Deckers Creek is a tributary stream in north-central West Virginia known for flowing through Monongalia and Preston counties before joining the Monongahela River at Morgantown.

Provenance (5 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_69e288be2c288190a3a46006945557f7 completed April 17, 2026, 7:23 p.m.
NER Named-entity recognition batch_69f1d5a7b5848190849e7a0f035465b3 completed April 29, 2026, 9:55 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0fc999c8588190a9e97af3be2fa02d completed May 22, 2026, 3:12 a.m.
NEDg Description generation batch_6a0fce0b7df88190b0304c274f485d26 completed May 22, 2026, 3:31 a.m.
NED2 Entity disambiguation (via description) batch_6a0fce8d480081909bcf9cadce8a11aa completed May 22, 2026, 3:33 a.m.
Created at: April 17, 2026, 9:42 p.m.