Triple

T37766187
Position Surface form Disambiguated ID Type / Status
Subject Seyhan E941420 entity
Predicate governingBody P46 FINISHED
Object Seyhan Municipality
Seyhan Municipality is the local government authority responsible for administering public services and urban management in the Seyhan district of Adana, Turkey.
E2248065 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: Seyhan Municipality | Statement: [Seyhan, governingBody, Seyhan 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: Seyhan Municipality
Triple: [Seyhan, governingBody, Seyhan Municipality]
Generated description
Seyhan Municipality is the local government authority responsible for administering public services and urban management in the Seyhan district of Adana, 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_69f76ee3251881909bb4451aad50752b completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fbaf19cc8c8190a818a92545e958ce completed May 6, 2026, 9:14 p.m.
NED1 Entity disambiguation (via context triple) batch_6a410cafec0c819082c03086e2371907 completed June 28, 2026, 11:59 a.m.
NEDg Description generation batch_6a410d8565e881908a8cd7eed4428c3f completed June 28, 2026, 12:03 p.m.
NED2 Entity disambiguation (via description) batch_6a410e09a0d48190aae6deab051064a3 completed June 28, 2026, 12:05 p.m.
Created at: May 3, 2026, 4:19 p.m.