Triple

T23748529
Position Surface form Disambiguated ID Type / Status
Subject Riffe Lake E586887 entity
Predicate namedAfter P63 FINISHED
Object Floyd B. Riffe
Floyd B. Riffe was a regional figure of sufficient local significance—likely a public official, community leader, or influential resident in Washington state—to have Riffe Lake named in his honor.
E2292595 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: Floyd B. Riffe | Statement: [Riffe Lake, namedAfter, Floyd B. Riffe]
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: Floyd B. Riffe
Triple: [Riffe Lake, namedAfter, Floyd B. Riffe]
Generated description
Floyd B. Riffe was a regional figure of sufficient local significance—likely a public official, community leader, or influential resident in Washington state—to have Riffe Lake named in his honor.

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_69e24908efb08190bf755c3a9b91f222 completed April 17, 2026, 2:51 p.m.
NER Named-entity recognition batch_69f1bcc058a88190b9addcbf3f063885 completed April 29, 2026, 8:09 a.m.
NED1 Entity disambiguation (via context triple) batch_6a79b1852d008190a81c5391ee2b07b3 completed Aug. 10, 2026, 11:09 a.m.
NEDg Description generation batch_6a79b943e98c819087f7a520a0ad47ea completed Aug. 10, 2026, 11:43 a.m.
NED2 Entity disambiguation (via description) batch_6a79ba69c68081909dd5f904b667979d completed Aug. 10, 2026, 11:47 a.m.
Created at: April 17, 2026, 7:12 p.m.