Triple

T27624050
Position Surface form Disambiguated ID Type / Status
Subject Kınık E696152 entity
Predicate hasLocalGovernment P2820 FINISHED
Object Kınık Municipality
Kınık Municipality is the local governing body responsible for administering public services and local affairs in the town and district of Kınık in Turkey.
E1784331 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: Kınık Municipality | Statement: [Kınık, hasLocalGovernment, Kınık Municipality]
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: Kınık Municipality
Triple: [Kınık, hasLocalGovernment, Kınık Municipality]
Generated description
Kınık Municipality is the local governing body responsible for administering public services and local affairs in the town and district of Kınık in Turkey.

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_69ef59092c8881908114ad184248cc46 completed April 27, 2026, 12:39 p.m.
NER Named-entity recognition batch_69f630df75248190a445f3c76dd5056f completed May 2, 2026, 5:14 p.m.
NED1 Entity disambiguation (via context triple) batch_6a12da86619c8190ade2ce33afd6a79d completed May 24, 2026, 11:01 a.m.
NEDg Description generation batch_6a12dc0707ec81908d3467bb9966030b completed May 24, 2026, 11:07 a.m.
NED2 Entity disambiguation (via description) batch_6a12dc96c6d88190ad9303a0a0de053a completed May 24, 2026, 11:10 a.m.
Created at: April 27, 2026, 2:16 p.m.