Triple
T31684504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aelia Constantia |
E808619
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman imperial woman |
C56886
|
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 imperial woman Context triple: [Aelia Constantia, instanceOf, Roman imperial woman]
-
A.
Roman empress
A Roman empress is the wife or female counterpart of a Roman emperor, often wielding significant political, social, and cultural influence within the imperial court and broader empire.
-
B.
Roman imperial princess
A Roman imperial princess is a female member of the emperor’s family whose status, marriages, and public image were used to secure dynastic legitimacy and political alliances within the Roman Empire.
-
C.
2nd-century Roman woman
A 2nd-century Roman woman is a female inhabitant of the Roman Empire during the 100s CE, whose daily life, legal status, and social roles were shaped by Roman family structures, class hierarchies, and regional cultural practices.
-
D.
late 4th-century Roman noblewoman
chosen
A late 4th-century Roman noblewoman is an elite female member of the Roman aristocracy who wields social, economic, and sometimes political influence through family networks, landownership, patronage, and participation in emerging Christian and traditional Roman cultural life.
-
E.
legendary Roman woman
A legendary Roman woman is a mythic or semi-historical female figure from ancient Rome whose life, virtues, or deeds became emblematic in Roman cultural memory and storytelling.
- F. None of above.
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_69f348ddcbc48190950cabcc25ff29b3 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:06 p.m.