Triple

T29985025
Position Surface form Disambiguated ID Type / Status
Subject Gooding County E761705 entity
Predicate formedFrom P402 FINISHED
Object Lincoln County
Lincoln County is a county in the U.S. state of Idaho known historically for its role in the administrative reorganization that led to the creation of several neighboring counties.
E779227 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: Lincoln County | Statement: [Gooding County, formedFrom, Lincoln County]
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: Lincoln County
Triple: [Gooding County, formedFrom, Lincoln County]
Generated description
Lincoln County is a county in the U.S. state of Idaho known historically for its role in the administrative reorganization that led to the creation of several neighboring counties.

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_69f2246851148190b8e76206db94b105 completed April 29, 2026, 3:31 p.m.
NER Named-entity recognition batch_69f678dc12c481909e88cb5cf37d5d29 completed May 2, 2026, 10:21 p.m.
NED1 Entity disambiguation (via context triple) batch_6a36117124f88190888c4f153dd136df completed June 20, 2026, 4:05 a.m.
NEDg Description generation batch_6a361347ca5081908e42385d827cbe7e completed June 20, 2026, 4:12 a.m.
NED2 Entity disambiguation (via description) batch_6a3613abb39881908fba9de844482934 completed June 20, 2026, 4:14 a.m.
Created at: April 29, 2026, 6:36 p.m.