Triple

T28502389
Position Surface form Disambiguated ID Type / Status
Subject Steeg E721268 entity
Predicate governedBy P46 FINISHED
Object municipal council of Steeg
The municipal council of Steeg is the local elected governing body responsible for making policy decisions and overseeing administration in the municipality of Steeg.
E1822524 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 Steeg | Statement: [Steeg, governedBy, municipal council of Steeg]
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 Steeg
Triple: [Steeg, governedBy, municipal council of Steeg]
Generated description
The municipal council of Steeg is the local elected governing body responsible for making policy decisions and overseeing administration in the municipality of Steeg.

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_69f01a5afdac8190ac6e72d5c100bd58 completed April 28, 2026, 2:24 a.m.
NER Named-entity recognition batch_69f64f44f82881909737e28390ab5e4a completed May 2, 2026, 7:23 p.m.
NED1 Entity disambiguation (via context triple) batch_6a1cac4a3524819089cfb71cffa79478 completed May 31, 2026, 9:46 p.m.
NEDg Description generation batch_6a1cacfc26bc8190ad65e3f8ef7d6d7b completed May 31, 2026, 9:49 p.m.
NED2 Entity disambiguation (via description) batch_6a1cadfcbe9481909de0ae4896d34859 completed May 31, 2026, 9:54 p.m.
Created at: April 28, 2026, 3:07 a.m.