Triple

T38354311
Position Surface form Disambiguated ID Type / Status
Subject Bolesław I of Opole E1046284 entity
Predicate sibling P363 FINISHED
Object Mieszko II the Fat
Mieszko II the Fat was a 13th-century Piast duke of Opole and Racibórz in Silesia, known for his role in the fragmented political landscape of medieval Poland.
E2288494 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: Mieszko II the Fat | Statement: [Bolesław I of Opole, sibling, Mieszko II the Fat]
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: Mieszko II the Fat
Triple: [Bolesław I of Opole, sibling, Mieszko II the Fat]
Generated description
Mieszko II the Fat was a 13th-century Piast duke of Opole and Racibórz in Silesia, known for his role in the fragmented political landscape of medieval Poland.

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_69f76e3a94fc81908edc175e8d259e80 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69fcc7338120819081cb46547d60f2cb completed May 7, 2026, 5:09 p.m.
NED1 Entity disambiguation (via context triple) batch_6a5a93af76fc8190a1d064b8f7bffe1a completed July 17, 2026, 8:42 p.m.
NEDg Description generation batch_6a5a947a3be48190bc8353025f111e70 completed July 17, 2026, 8:45 p.m.
NED2 Entity disambiguation (via description) batch_6a5a955076e081909c0cc0a80a39fa22 completed July 17, 2026, 8:49 p.m.
Created at: May 3, 2026, 4:31 p.m.