Triple

T29495044
Position Surface form Disambiguated ID Type / Status
Subject Valley County, Idaho E748196 entity
Predicate containsSettlement P847 FINISHED
Object Donnelly, Idaho
Donnelly, Idaho is a small rural city in west-central Idaho known as a gateway to outdoor recreation in the Long Valley area near Cascade and McCall.
E1896389 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: Donnelly, Idaho | Statement: [Valley County, Idaho, containsSettlement, Donnelly, Idaho]
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: Donnelly, Idaho
Triple: [Valley County, Idaho, containsSettlement, Donnelly, Idaho]
Generated description
Donnelly, Idaho is a small rural city in west-central Idaho known as a gateway to outdoor recreation in the Long Valley area near Cascade and McCall.

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_69f0bd448c6881908aa6b475cefd5ddc completed April 28, 2026, 1:59 p.m.
NER Named-entity recognition batch_69f66c0e07e48190a1a5554455766b30 completed May 2, 2026, 9:26 p.m.
NED1 Entity disambiguation (via context triple) batch_6a27320a2ce0819085c08deedd0ac159 completed June 8, 2026, 9:20 p.m.
NEDg Description generation batch_6a27337dd0508190afedc1921edc2cf6 completed June 8, 2026, 9:26 p.m.
NED2 Entity disambiguation (via description) batch_6a2733ea68648190ae0baecf93506db6 completed June 8, 2026, 9:28 p.m.
Created at: April 28, 2026, 4:17 p.m.