Triple
T30531016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Tetrarchy |
E776998
|
entity |
| Predicate | hasInstabilityCause |
P104566
|
FINISHED |
| Object | usurpation of Maxentius in Rome |
—
|
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: usurpation of Maxentius in Rome | Statement: [Second Tetrarchy, hasInstabilityCause, usurpation of Maxentius in Rome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInstabilityCause Context triple: [Second Tetrarchy, hasInstabilityCause, usurpation of Maxentius in Rome]
-
A.
reasonForInstability
chosen
Indicates the cause or underlying factor that leads to an entity’s instability or lack of steadiness.
-
B.
hasCause
Indicates that one entity is the reason for, or brings about, the occurrence or existence of another entity or event.
-
C.
hasCauseOfVariability
Indicates a relationship where one factor or condition is identified as the source or driver of variation observed in another.
-
D.
isUnstable
Indicates that the subject lacks stability or consistency, often changing, fluctuating, or failing to remain in a steady state.
-
E.
haveStabilityDeterminedBy
Indicates that the stability of one entity is determined or governed by another specified factor or entity.
- 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_69f2249c11508190ae7e955755ccfb01 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fef5cf8da881908260ec633830375d |
completed | May 9, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69fef455e40481909861c82007b79bc0 |
completed | May 9, 2026, 8:46 a.m. |
Created at: April 29, 2026, 8:18 p.m.