Triple

T25287677
Position Surface form Disambiguated ID Type / Status
Subject Şehzade Orhan E633987 entity
Predicate father P120 FINISHED
Object Şehzade Mustafa
Şehzade Mustafa was an Ottoman prince and heir apparent whose execution by his father, Sultan Suleiman the Magnificent, became one of the most tragic and controversial events in Ottoman history.
E152777 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: Şehzade Mustafa | Statement: [Şehzade Orhan, father, Şehzade Mustafa]
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: Şehzade Mustafa
Triple: [Şehzade Orhan, father, Şehzade Mustafa]
Generated description
Şehzade Mustafa was an Ottoman prince and heir apparent whose execution by his father, Sultan Suleiman the Magnificent, became one of the most tragic and controversial events in Ottoman history.

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_69e75a9402fc81909362ca85277c06d9 completed April 21, 2026, 11:08 a.m.
NER Named-entity recognition batch_69f48e09f11481908c65718e522a3e02 completed May 1, 2026, 11:27 a.m.
NED1 Entity disambiguation (via context triple) batch_6a108971fe408190925d5b7c2c3e9801 completed May 22, 2026, 4:50 p.m.
NEDg Description generation batch_6a108a2504b8819085f07ef035e63915 completed May 22, 2026, 4:53 p.m.
NED2 Entity disambiguation (via description) batch_6a108b0184288190bf29fb5ea42b7c5f completed May 22, 2026, 4:57 p.m.
Created at: April 21, 2026, 1:19 p.m.