Triple
T32171400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Despot of Epirus |
E821716
|
entity |
| Predicate | hasTitleHolderFromDynasty |
P72476
|
FINISHED |
| Object | Komnenos Doukas dynasty |
—
|
NE NERFINISHED |
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: Komnenos Doukas dynasty | Statement: [Despot of Epirus, hasTitleHolderFromDynasty, Komnenos Doukas dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTitleHolderFromDynasty Context triple: [Despot of Epirus, hasTitleHolderFromDynasty, Komnenos Doukas dynasty]
-
A.
correspondsToReignTitleHolder
Indicates that a given reign or period of rule is associated with, and held by, a specific title holder.
-
B.
monarchicTitleHolderOf
Indicates that one entity holds a monarchic title associated with another entity (such as a realm, position, or office).
-
C.
titleHolderDynasticHouse
chosen
Indicates the dynastic house or ruling family that holds a particular title.
-
D.
hasHeirApparentTitle
Indicates that an entity holds a title designating them as the officially recognized heir apparent to another entity’s position or rank.
-
E.
hasTitleHeirApparentStyle
Indicates that an entity holds the formal style or designation associated with being the heir apparent to a title.
- F. None of above.
Provenance (3 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_69f3490699a48190bbef96b198e8fade |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
Created at: May 1, 2026, 12:33 a.m.