Triple
T15603264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doukas dynasty |
E375086
|
entity |
| Predicate | endOfDirectImperialReign |
P59019
|
FINISHED |
| Object | 1078 |
—
|
LITERAL 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: 1078 | Statement: [Doukas dynasty, endOfDirectImperialReign, 1078]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endOfDirectImperialReign Context triple: [Doukas dynasty, endOfDirectImperialReign, 1078]
-
A.
endOfReign
Indicates the point in time or event at which a ruler’s or leader’s period of authority or reign concludes.
-
B.
dynastyEndedWith
chosen
Indicates that a particular dynasty concluded or came to an end with the specified ruler, event, or time period.
-
C.
endEmperor
Indicates the point or event at which an individual's tenure or status as emperor comes to an end.
-
D.
coEmperorEnd
Indicates that one entity’s tenure as co-emperor with another entity comes to an end at a specific point in time.
-
E.
thirdHolderReignEnd
Indicates the date or point in time when the reign or tenure of the third holder of a title, office, or position comes to an end.
- 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_69d85cce25008190b13b52745fbd719b |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e6399d88190b2c3e781667666d4 |
completed | April 16, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69deda844af081909e658ebc9d9b403d |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:12 a.m.