Triple

T29104195
Position Surface form Disambiguated ID Type / Status
Subject Ruma E736717 entity
Predicate hasLocalGovernment P2820 FINISHED
Object Municipality of Ruma
The Municipality of Ruma is a local self-governing administrative unit in Serbia that encompasses the town of Ruma and surrounding settlements within the Srem District.
E1852164 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: Municipality of Ruma | Statement: [Ruma, hasLocalGovernment, Municipality of Ruma]
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: Municipality of Ruma
Triple: [Ruma, hasLocalGovernment, Municipality of Ruma]
Generated description
The Municipality of Ruma is a local self-governing administrative unit in Serbia that encompasses the town of Ruma and surrounding settlements within the Srem District.

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_69f077ec765c81909474c88bcc8bab43 completed April 28, 2026, 9:03 a.m.
NER Named-entity recognition batch_69f661b842808190ac168c6f3d40d23c completed May 2, 2026, 8:42 p.m.
NED1 Entity disambiguation (via context triple) batch_6a2550506784819084c6b8a89f53c670 completed June 7, 2026, 11:04 a.m.
NEDg Description generation batch_6a2554b16b8481908ffb9447fb3f35a5 completed June 7, 2026, 11:23 a.m.
NED2 Entity disambiguation (via description) batch_6a2558e91cc0819081c9baa7e53d6f7e completed June 7, 2026, 11:41 a.m.
Created at: April 28, 2026, 11:14 a.m.