Triple
T12937657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucius Munatius Plancus |
E309555
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the gens Munatia |
C32130
|
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: member of the gens Munatia Context triple: [Lucius Munatius Plancus, instanceOf, member of the gens Munatia]
-
A.
member of the gens Claudia
A member of the gens Claudia is an individual belonging to the ancient Roman patrician (and later plebeian) family Claudia, known for its prominent political, military, and social influence in the Roman Republic and Empire.
-
B.
member of the gens Cornelia
A member of the gens Cornelia is an individual belonging to the prominent and influential Cornelii family of ancient Rome, known for producing many notable political and military leaders.
-
C.
member of the gens Aemilia
A member of the gens Aemilia is an individual belonging to the ancient Roman patrician family Aemilia, known for its political influence, consular magistracies, and longstanding prominence in Roman public life.
-
D.
member of the gens Pompeia
A member of the gens Pompeia is an individual belonging by birth or adoption to the ancient Roman plebeian family Pompeia, sharing its name, lineage, and social identity within Roman society.
-
E.
member of the gens Caecilia
A member of the gens Caecilia is an individual belonging to the ancient Roman plebeian family (gens) Caecilia, identified by the shared nomen "Caecilius" and associated with its social status, traditions, and political legacy.
- 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_69d7bdfa933c8190b5a27aa4a08a19b7 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:43 p.m.