Triple

T27393950
Position Surface form Disambiguated ID Type / Status
Subject Eyüpsultan district E691621 entity
Predicate contains P35 FINISHED
Object Akşemsettin neighborhood
Akşemsettin neighborhood is a residential quarter of Istanbul, Turkey, situated within the historic Eyüpsultan district on the European side of the city.
E1799715 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: Akşemsettin neighborhood | Statement: [Eyüpsultan district, contains, Akşemsettin neighborhood]
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: Akşemsettin neighborhood
Triple: [Eyüpsultan district, contains, Akşemsettin neighborhood]
Generated description
Akşemsettin neighborhood is a residential quarter of Istanbul, Turkey, situated within the historic Eyüpsultan district on the European side of the city.

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_69ef5204f7048190bf226a129858fc5b completed April 27, 2026, 12:09 p.m.
NER Named-entity recognition batch_69f62caf1be88190b61397557e09c0e9 completed May 2, 2026, 4:56 p.m.
NED1 Entity disambiguation (via context triple) batch_6a15d773f2408190ba9348c1972bb483 completed May 26, 2026, 5:25 p.m.
NEDg Description generation batch_6a15d82ac0fc819082a575f3f11f25da completed May 26, 2026, 5:28 p.m.
NED2 Entity disambiguation (via description) batch_6a15d8e229e88190aaf00c672b1bf5da completed May 26, 2026, 5:31 p.m.
Created at: April 27, 2026, 12:27 p.m.