Triple
T3270952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Germanicus |
E68646
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | imperial prince of Rome |
C13748
|
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: imperial prince of Rome Context triple: [Germanicus, instanceOf, imperial prince of Rome]
-
A.
Western Roman emperor
A Western Roman emperor is the sovereign ruler of the western half of the Roman Empire, holding supreme political, military, and religious authority from the late 3rd to the late 5th century CE.
-
B.
regent of the Eastern Roman Empire
A regent of the Eastern Roman Empire is an appointed or self-declared authority who governs the empire on behalf of a reigning but underage, absent, incapacitated, or otherwise unable emperor, wielding imperial power without holding the imperial title.
-
C.
usurper Roman emperor
A usurper Roman emperor is an individual who illegitimately seizes imperial power, typically through rebellion or military support, without lawful succession or recognition by established authorities.
-
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.
Eastern Roman emperor
An Eastern Roman emperor is the sovereign ruler of the eastern portion of the Roman Empire, later known as the Byzantine Empire, wielding supreme political, military, and religious authority.
- 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_69ad859b54f881909bf530d549caf2fd |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:09 p.m.