Triple
T1807074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Appius Claudius Caecus |
E40245
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the gens Claudia |
C9119
|
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 Claudia Context triple: [Appius Claudius Caecus, instanceOf, member of the gens Claudia]
-
A.
Herodian dynasty member
A Herodian dynasty member is an individual belonging to the ruling family established by Herod the Great, which governed Judea and surrounding regions under Roman authority during the late first century BCE and early first century CE.
-
B.
Roman senator
A Roman senator is a high-ranking political figure in ancient Rome who participates in legislative, advisory, and administrative decision-making within the Senate, influencing the governance and policies of the Roman state.
-
C.
Roman consul
A Roman consul was one of the two annually elected chief magistrates of the Roman Republic (and later an important office in the Empire), holding supreme civil and military authority and presiding over the Senate and assemblies.
-
D.
Theatine priest
A Theatine priest is a member of the Clerics Regular of the Theatines, a Catholic religious order of priests devoted to reforming the clergy and promoting piety through strict communal life, pastoral work, and liturgical service.
-
E.
member of the House of Savoy
A member of the House of Savoy is an individual belonging by birth or marriage to the historic European royal dynasty that ruled territories including Savoy, Sardinia, and eventually unified Italy.
- 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_69a88643a3388190a612f2ebe1fb29e7 |
completed | March 4, 2026, 7:21 p.m. |
Created at: March 4, 2026, 7:32 p.m.