Triple

T34485647
Position Surface form Disambiguated ID Type / Status
Subject Mińsk Mazowiecki E885311 entity
Predicate isSeatOf P62 FINISHED
Object Mińsk County authorities
Mińsk County authorities are the local government bodies responsible for administering Mińsk County in the Masovian Voivodeship of east-central Poland.
E2098687 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: Mińsk County authorities | Statement: [Mińsk Mazowiecki, isSeatOf, Mińsk County authorities]
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: Mińsk County authorities
Triple: [Mińsk Mazowiecki, isSeatOf, Mińsk County authorities]
Generated description
Mińsk County authorities are the local government bodies responsible for administering Mińsk County in the Masovian Voivodeship of east-central Poland.

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_69f349c947fc81909d30b53c194d6ea1 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f71ce9db0c8190afdcc14cf3b3ac21 completed May 3, 2026, 10:01 a.m.
NED1 Entity disambiguation (via context triple) batch_6a37213be340819096cb4f6ab8481df9 completed June 20, 2026, 11:24 p.m.
NEDg Description generation batch_6a37222a589c81909ce775d02c13f6b6 completed June 20, 2026, 11:28 p.m.
NED2 Entity disambiguation (via description) batch_6a3722b425808190a8453a3e71d14066 completed June 20, 2026, 11:31 p.m.
Created at: May 1, 2026, 2:01 a.m.