Triple

T37682013
Position Surface form Disambiguated ID Type / Status
Subject Büyükorhan E938258 entity
Predicate governingBody P46 FINISHED
Object Büyükorhan Municipality
Büyükorhan Municipality is the local governmental authority responsible for administering public services and local affairs in the district of Büyükorhan, Turkey.
E2241637 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: Büyükorhan Municipality | Statement: [Büyükorhan, governingBody, Büyükorhan 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: Büyükorhan Municipality
Triple: [Büyükorhan, governingBody, Büyükorhan Municipality]
Generated description
Büyükorhan Municipality is the local governmental authority responsible for administering public services and local affairs in the district of Büyükorhan, 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_69f76ed881408190bc62a969530a4a53 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fbadf966f88190b4a3be1500b0f958 completed May 6, 2026, 9:09 p.m.
NED1 Entity disambiguation (via context triple) batch_6a40f16d13d88190a734988467e562b6 completed June 28, 2026, 10:03 a.m.
NEDg Description generation batch_6a40f2540f848190b7ac57b130d8234d completed June 28, 2026, 10:07 a.m.
NED2 Entity disambiguation (via description) batch_6a40f2dd54488190b0da6cb656706f54 completed June 28, 2026, 10:09 a.m.
Created at: May 3, 2026, 4:18 p.m.