Triple
T30874266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Martinian |
E786431
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman co-emperor |
C59564
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Roman co-emperor Context triple: [Martinian, instanceOf, Roman co-emperor]
-
A.
imperial prince of Rome
An imperial prince of Rome is a male member of the ruling emperor’s family, often positioned as a potential heir and endowed with high status, privileges, and political influence within the Roman imperial hierarchy.
-
B.
regent of the Western Roman Empire
A regent of the Western Roman Empire was an individual who governed the empire on behalf of an underage, absent, or otherwise incapacitated Western Roman emperor, exercising imperial authority without holding the imperial title.
-
C.
emperor of the Romans
The "emperor of the Romans" is the supreme sovereign who claims ultimate political and often religious authority over the Roman people and their empire, embodying the continuity and legitimacy of Roman imperial rule.
-
D.
4th-century Roman emperor
A 4th-century Roman emperor is a sovereign ruler of the Roman Empire during the 300s CE, navigating military, religious, and administrative transformations that reshaped the ancient Mediterranean world.
-
E.
legendary Roman prince
A legendary Roman prince is a semi-mythical noble figure from ancient Rome, often depicted as embodying idealized virtues such as bravery, honor, and leadership, and frequently associated with foundational or heroic tales of the Roman state.
- F. None of above. chosen
Provenance (1 batch)
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_69f224bae17c8190bb3a6a28e3d019df |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:48 p.m.