Triple

T35032582
Position Surface form Disambiguated ID Type / Status
Subject megas domestikos E1010818 entity
Predicate positionHeldBy P8 FINISHED
Object Alexios Raoul Petraliphas
Alexios Raoul Petraliphas was a high-ranking Byzantine noble and military commander who served as one of the empire’s leading generals.
E2175179 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: Alexios Raoul Petraliphas | Statement: [megas domestikos, positionHeldBy, Alexios Raoul Petraliphas]
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: Alexios Raoul Petraliphas
Triple: [megas domestikos, positionHeldBy, Alexios Raoul Petraliphas]
Generated description
Alexios Raoul Petraliphas was a high-ranking Byzantine noble and military commander who served as one of the empire’s leading generals.

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_69f76dcea02c81908542a223f6d5059f completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f78549d7fc8190adedcef3282becba completed May 3, 2026, 5:26 p.m.
NED1 Entity disambiguation (via context triple) batch_6a394d135fa481909d7adbe64d1392e9 completed June 22, 2026, 2:56 p.m.
NEDg Description generation batch_6a395131720081908b5a12778cb8e085 completed June 22, 2026, 3:13 p.m.
NED2 Entity disambiguation (via description) batch_6a3952df9ca481909efc563734d14a31 completed June 22, 2026, 3:21 p.m.
Created at: May 3, 2026, 4:01 p.m.