Triple
T30305398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Augusta (Roman Empire) |
E770766
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman imperial honorific |
C10539
|
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 honorific Context triple: [Augusta (Roman Empire), instanceOf, Roman imperial honorific]
-
A.
ancient Roman title
chosen
An ancient Roman title is a formal designation or rank used in Roman society and government to denote an individual's official role, status, or authority within the political, military, religious, or social hierarchy.
-
B.
Roman official
A Roman official is a government functionary of ancient Rome responsible for administering laws, finances, justice, or public works within the Republic or Empire.
-
C.
Roman name
A Roman name is a personal designation used in ancient Rome, typically composed of multiple parts (such as praenomen, nomen, and cognomen) that indicated an individual's given name, family lineage, and sometimes personal traits or achievements.
-
D.
Roman cognomen
A Roman cognomen is the third part of a traditional Roman male name, originally a nickname that evolved into a hereditary family branch identifier within a gens.
-
E.
Byzantine noble title
A Byzantine noble title is a formal rank or honorific designation within the hierarchical aristocratic and court system of the Byzantine Empire, signifying status, authority, and often specific administrative or military responsibilities.
- 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_69f224881b948190b8c4921b250a44a3 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:49 p.m.