Triple
T32658030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iovius |
E834917
|
entity |
| Predicate | roleInTetrarchy |
P31447
|
FINISHED |
| Object | designated Diocletian as the Jovian emperor |
—
|
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: designated Diocletian as the Jovian emperor | Statement: [Iovius, roleInTetrarchy, designated Diocletian as the Jovian emperor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInTetrarchy Context triple: [Iovius, roleInTetrarchy, designated Diocletian as the Jovian emperor]
-
A.
tetrarchyMemberOf
Indicates that an entity is a member of a governing body or group composed of four rulers or leaders.
-
B.
positionInTetrarchy
chosen
Indicates the specific role or rank an individual holds within a four-part governing or leadership structure (a tetrarchy).
-
C.
roleUnderCarausius
Indicates that one entity held a role, position, or office subordinate to or under the authority of Carausius.
-
D.
numberOfCaesaresInTetrarchy
Indicates the quantity of distinct rulers titled "Caesar" within a given instance of the Tetrarchy system.
-
E.
RomanCommander
Indicates a relationship where an entity holds the role or position of a commander within a Roman military or organizational context.
- 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_69f3492f72248190ba42fa596aea50e1 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a00474f08908190bc8ae3b320ec887b |
completed | May 10, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_6a0045dc3bd48190a9e0520f3ef3f067 |
completed | May 10, 2026, 8:46 a.m. |
Created at: May 1, 2026, 1:08 a.m.