Triple

T35030768
Position Surface form Disambiguated ID Type / Status
Subject Irene of Hungary E1010473 entity
Predicate otherName P39 FINISHED
Object Irene Komnene
Irene Komnene, born Piroska of Hungary, was a Hungarian princess who became Byzantine empress consort through her marriage to Emperor John II Komnenos in the 12th century.
E2125944 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: Irene Komnene | Statement: [Irene of Hungary, otherName, Irene Komnene]
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: Irene Komnene
Triple: [Irene of Hungary, otherName, Irene Komnene]
Generated description
Irene Komnene, born Piroska of Hungary, was a Hungarian princess who became Byzantine empress consort through her marriage to Emperor John II Komnenos in the 12th century.

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_69f76dccf0108190af43b465d3750196 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f785468bc88190bece118c6e900400 completed May 3, 2026, 5:26 p.m.
NED1 Entity disambiguation (via context triple) batch_6a37cfddddcc81909de4990f933113e7 completed June 21, 2026, 11:49 a.m.
NEDg Description generation batch_6a37d09160108190adcf3b1a85a0e8a2 completed June 21, 2026, 11:52 a.m.
NED2 Entity disambiguation (via description) batch_6a37d1d5dad081908a0f25b28428977b completed June 21, 2026, 11:58 a.m.
Created at: May 3, 2026, 4:01 p.m.