Triple
T5903431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theodora |
E131281
|
entity |
| Predicate | hadPowerType |
P66833
|
FINISHED |
| Object | de facto co-ruler with Justinian I |
—
|
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: de facto co-ruler with Justinian I | Statement: [Theodora, hadPowerType, de facto co-ruler with Justinian I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadPowerType Context triple: [Theodora, hadPowerType, de facto co-ruler with Justinian I]
-
A.
hasPower
Indicates that one entity possesses authority, control, or influence over another entity or over a particular domain or resource.
-
B.
usesPowerType
Indicates that one entity operates or functions by means of a specified type or source of power.
-
C.
hasMotivePowerType
Indicates that an entity (such as a vehicle or machine) operates using a specified type of motive power (e.g., electric, diesel, steam).
-
D.
hasNumberOfPowers
Indicates the quantity of distinct powers or abilities that an entity possesses.
-
E.
hasTypeOfPowerRegulated
Indicates that one entity exercises a specific kind of power or authority that is subject to regulation or control by another entity or governing framework.
- F. None of above. chosen
Provenance (4 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_69c0085864a88190a569c05ff7d65f29 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03ee10b308190afe38b904ae7c5f7 |
completed | March 22, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69c0334fcf6481908e8e74105de9d49b |
completed | March 22, 2026, 6:22 p.m. |
| PDg | Predicate description generation | batch_69c03edf98b881908e9dbc03d3fd6218 |
completed | March 22, 2026, 7:11 p.m. |
Created at: March 22, 2026, 3:58 p.m.