Triple

T34420549
Position Surface form Disambiguated ID Type / Status
Subject Tarxien E883513 entity
Predicate hasLocalCouncil P3379 FINISHED
Object Tarxien Local Council
Tarxien Local Council is the elected local governing body responsible for administering municipal services and community affairs in the town of Tarxien, Malta.
E2094837 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: Tarxien Local Council | Statement: [Tarxien, hasLocalCouncil, Tarxien 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: Tarxien Local Council
Triple: [Tarxien, hasLocalCouncil, Tarxien Local Council]
Generated description
Tarxien Local Council is the elected local governing body responsible for administering municipal services and community affairs in the town of Tarxien, Malta.

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_69f349c2e3b88190a67834eb5bcffeaf completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f718dab0608190b1c39c3cddd1cc03 completed May 3, 2026, 9:43 a.m.
NED1 Entity disambiguation (via context triple) batch_6a370dd7f00c819095cd07a715aced03 completed June 20, 2026, 10:02 p.m.
NEDg Description generation batch_6a370ed2f1e08190b7f7d5de639e777d completed June 20, 2026, 10:06 p.m.
NED2 Entity disambiguation (via description) batch_6a370f7d1720819084c181648df5cfee completed June 20, 2026, 10:09 p.m.
Created at: May 1, 2026, 2 a.m.