Triple

T38638821
Position Surface form Disambiguated ID Type / Status
Subject Pucking E938534 entity
Predicate governedBy P46 FINISHED
Object municipal council of Pucking
The municipal council of Pucking is the local representative governing body responsible for making decisions and setting policies for the municipality of Pucking.
E2278589 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: municipal council of Pucking | Statement: [Pucking, governedBy, municipal council of Pucking]
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: municipal council of Pucking
Triple: [Pucking, governedBy, municipal council of Pucking]
Generated description
The municipal council of Pucking is the local representative governing body responsible for making decisions and setting policies for the municipality of Pucking.

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_69f76ed948ec81908ce7811608a8f359 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fcd9b8e3c88190a3a56e103483aba0 completed May 7, 2026, 6:28 p.m.
NED1 Entity disambiguation (via context triple) batch_6a41f4591e748190b9bba4f7671ed068 completed June 29, 2026, 4:28 a.m.
NEDg Description generation batch_6a41f510ea6481908491ca410f6f7ec3 completed June 29, 2026, 4:31 a.m.
NED2 Entity disambiguation (via description) batch_6a41f6229fb8819099ba86f2db3ae6d1 completed June 29, 2026, 4:35 a.m.
Created at: May 3, 2026, 4:32 p.m.