Triple

T30541802
Position Surface form Disambiguated ID Type / Status
Subject Bakhdida E777298 entity
Predicate hasAlternativeName P39 FINISHED
Object Baghdida
Baghdida is a historically Assyrian Christian town in northern Iraq, known for its ancient churches and significant role in the cultural and religious life of the Nineveh Plains.
E1928063 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: Baghdida | Statement: [Bakhdida, hasAlternativeName, Baghdida]
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: Baghdida
Triple: [Bakhdida, hasAlternativeName, Baghdida]
Generated description
Baghdida is a historically Assyrian Christian town in northern Iraq, known for its ancient churches and significant role in the cultural and religious life of the Nineveh Plains.

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_69f2249d183c8190b79937c1768d2163 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f6888c052081909c1117592dac5a59 completed May 2, 2026, 11:28 p.m.
NED1 Entity disambiguation (via context triple) batch_6a2898c1cedc819091a200a48cdba8e6 completed June 9, 2026, 10:50 p.m.
NEDg Description generation batch_6a2899be081c8190ba9cd748063e8dc0 completed June 9, 2026, 10:54 p.m.
NED2 Entity disambiguation (via description) batch_6a289ac7f570819094b7940133c5ac52 completed June 9, 2026, 10:59 p.m.
Created at: April 29, 2026, 8:19 p.m.