Triple
T31118306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Phocas |
E793151
|
entity |
| Predicate | usurperDynasty |
P168663
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [House of Phocas, usurperDynasty, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usurperDynasty Context triple: [House of Phocas, usurperDynasty, true]
-
A.
regentDynasty
Indicates that one entity served as the ruling dynasty or regent house governing on behalf of another entity (such as a realm, monarch, or territory).
-
B.
usurpsThroneFrom
Indicates that one entity seizes control of a throne or rulership position that previously belonged to another entity, typically by force or illegitimate means.
-
C.
notableUsurperDuringReign
Indicates that a specified person is a notable usurper who attempted to seize or seized power during the reign of a particular ruler.
-
D.
consideredUsurper
chosen
Indicates that one entity is regarded or treated by another as an illegitimate holder of power, position, or authority.
-
E.
formerRulerHouse
Indicates that a person once ruled on behalf of, or as a member of, a particular ruling house or dynasty but no longer holds that ruling position.
- 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_69f224d0a7688190af3fe3e6e26d01ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:04 p.m.