Triple

T38408749
Position Surface form Disambiguated ID Type / Status
Subject Brodnica E901411 entity
Predicate governingBody P46 FINISHED
Object Brodnica town council
Brodnica town council is the elected municipal governing body responsible for local legislation, administration, and public services in the town of Brodnica, Poland.
E2267330 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: Brodnica town council | Statement: [Brodnica, governingBody, Brodnica town council]
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: Brodnica town council
Triple: [Brodnica, governingBody, Brodnica town council]
Generated description
Brodnica town council is the elected municipal governing body responsible for local legislation, administration, and public services in the town of Brodnica, Poland.

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_69f76e61e79c81908b787d83b46ab92b completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69fccd615934819086d54e49f1b92bd9 completed May 7, 2026, 5:35 p.m.
NED1 Entity disambiguation (via context triple) batch_6a41b2bfe8488190b66ca3d1bc311d0f completed June 28, 2026, 11:48 p.m.
NEDg Description generation batch_6a41b39670d8819082a9ca82e2d86b5e completed June 28, 2026, 11:51 p.m.
NED2 Entity disambiguation (via description) batch_6a41b41248648190924d0ea43a48dfc7 completed June 28, 2026, 11:53 p.m.
Created at: May 3, 2026, 4:31 p.m.