Triple

T37851849
Position Surface form Disambiguated ID Type / Status
Subject Balzan E944073 entity
Predicate governingBody P46 FINISHED
Object Balzan Local Council
Balzan Local Council is the local governmental authority responsible for administering and managing municipal services and community affairs in the Maltese village of Balzan.
E2245387 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: Balzan Local Council | Statement: [Balzan, governingBody, Balzan Local 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: Balzan Local Council
Triple: [Balzan, governingBody, Balzan Local Council]
Generated description
Balzan Local Council is the local governmental authority responsible for administering and managing municipal services and community affairs in the Maltese village of Balzan.

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_69f76eed4d9c81908b1b71ba9e3b61fe completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fbb24ac0dc819099fb3a2d4551371c completed May 6, 2026, 9:27 p.m.
NED1 Entity disambiguation (via context triple) batch_6a40fb9448fc8190955703807085f889 completed June 28, 2026, 10:46 a.m.
NEDg Description generation batch_6a40fc690fe08190b4ceaadfe93be2a3 completed June 28, 2026, 10:50 a.m.
NED2 Entity disambiguation (via description) batch_6a40fce18ec08190946c064d27fcf5ad completed June 28, 2026, 10:52 a.m.
Created at: May 3, 2026, 4:19 p.m.