Triple

T38188910
Position Surface form Disambiguated ID Type / Status
Subject Linden, Iowa E1005396 entity
Predicate governingBody P46 FINISHED
Object Linden town government
Linden town government is the local municipal authority responsible for administering public services, ordinances, and community affairs in Linden, Iowa.
E2259934 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: Linden town government | Statement: [Linden, Iowa, governingBody, Linden town government]
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: Linden town government
Triple: [Linden, Iowa, governingBody, Linden town government]
Generated description
Linden town government is the local municipal authority responsible for administering public services, ordinances, and community affairs in Linden, Iowa.

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_69f76dbc22c481908139b694ffde7a0c completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69fcb11599588190b45185a95cd61d82 completed May 7, 2026, 3:34 p.m.
NED1 Entity disambiguation (via context triple) batch_6a417b3fae14819083c6191c451d97fd completed June 28, 2026, 7:51 p.m.
NEDg Description generation batch_6a417cd7acc88190bd7681188167ea06 completed June 28, 2026, 7:58 p.m.
NED2 Entity disambiguation (via description) batch_6a417d439728819098feaa986cae3336 completed June 28, 2026, 8 p.m.
Created at: May 3, 2026, 4:29 p.m.