Triple
T26916182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman jurists |
E677522
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Roman profession |
C12577
|
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: ancient Roman profession Context triple: [Roman jurists, instanceOf, ancient Roman profession]
-
A.
ancient Roman title
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.
ancient Roman paramilitary corps
An ancient Roman paramilitary corps is a semi-military organization operating alongside or outside the formal legions, tasked with security, policing, or specialized combat roles in support of Roman state authority.
-
C.
person of the early Roman Empire
A person of the early Roman Empire is an individual living under Roman rule during the first centuries BCE–CE, shaped by Roman law, social hierarchy, imperial politics, and a cosmopolitan Mediterranean culture.
-
D.
ancient Roman
chosen
An ancient Roman is a person from the civilization of Rome between roughly the 8th century BCE and the 5th century CE, characterized by its distinctive language, culture, politics, and engineering achievements.
-
E.
member of the Roman nobility
A member of the Roman nobility is an individual belonging to the elite social class of ancient Rome, distinguished by hereditary status, political influence, and privileged legal and economic rights.
- 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_69eee9bdebc48190ba90a12a63e09c73 |
completed | April 27, 2026, 4:44 a.m. |
Created at: April 27, 2026, 6:04 a.m.