Triple
T32567903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucius Afranius |
E832421
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | supporter of Pompey |
C43952
|
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: supporter of Pompey Context triple: [Lucius Afranius, instanceOf, supporter of Pompey]
-
A.
follower of Pompey
chosen
A follower of Pompey is an individual who supported and aligned with the Roman general and statesman Gnaeus Pompeius Magnus (Pompey the Great), particularly in his political, military, or ideological causes.
-
B.
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.
-
C.
associate of Julius Caesar
An associate of Julius Caesar is any individual who maintained a significant political, military, or personal relationship with Caesar, influencing or being influenced by his rise and rule in the late Roman Republic.
-
D.
friend of Scipio Aemilianus
A "friend of Scipio Aemilianus" is an individual who belonged to the influential intellectual and political circle surrounding the Roman general and statesman Scipio Aemilianus, sharing close personal ties, cultural interests, and often aligned political views.
-
E.
associate of Augustus
An associate of Augustus is an individual who maintained a close political, military, or personal relationship with the first Roman emperor, contributing to or benefiting from his rise and consolidation of power.
- 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_69f34927bb308190ad94da1b11cad13c |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1:03 a.m.