Triple

T29572089
Position Surface form Disambiguated ID Type / Status
Subject Shamash-shum-ukin E753340 entity
Predicate sibling P363 FINISHED
Object Serua-eterat
Serua-eterat was an Assyrian royal princess of the Neo-Assyrian Empire, known as a daughter of King Esarhaddon and sister of rulers such as Shamash-shum-ukin and Ashurbanipal.
E1873623 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: Serua-eterat | Statement: [Shamash-shum-ukin, sibling, Serua-eterat]
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: Serua-eterat
Triple: [Shamash-shum-ukin, sibling, Serua-eterat]
Generated description
Serua-eterat was an Assyrian royal princess of the Neo-Assyrian Empire, known as a daughter of King Esarhaddon and sister of rulers such as Shamash-shum-ukin and Ashurbanipal.

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_69f0ef7fcb4881908a933110adb9bda1 completed April 28, 2026, 5:33 p.m.
NER Named-entity recognition batch_69f66d47de5481908e4f3ae9fae613c3 completed May 2, 2026, 9:31 p.m.
NED1 Entity disambiguation (via context triple) batch_6a262d6cb7c48190a23bd341d90bd91e completed June 8, 2026, 2:48 a.m.
NEDg Description generation batch_6a2631b9deb48190b1c85040301cd819 completed June 8, 2026, 3:06 a.m.
NED2 Entity disambiguation (via description) batch_6a263366e60c8190bd1bba907a72899c completed June 8, 2026, 3:13 a.m.
Created at: April 28, 2026, 5:59 p.m.