Triple
T8311852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Comitia Curiata (early period, debated) |
E194608
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman religious assembly |
C13466
|
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 religious assembly Context triple: [Comitia Curiata (early period, debated), instanceOf, Roman religious assembly]
-
A.
event in ancient Rome
chosen
An event in ancient Rome is a specific occurrence or happening—such as a political assembly, religious festival, public spectacle, or military action—situated in Roman society and time that holds social, cultural, or historical significance.
-
B.
ancient Roman temple
An ancient Roman temple is a monumental religious structure, typically rectangular with a columned portico and elevated podium, dedicated to one or more deities and serving as a focal point for public worship and civic identity in Roman society.
-
C.
Roman theatre
A Roman theatre is a large, semi-circular open-air structure designed for public performances, featuring tiered seating, an orchestra, and an elaborately decorated stage building.
-
D.
Roman censor
A Roman censor was a high-ranking magistrate responsible for conducting the census, overseeing public morals, and managing certain aspects of state finances and public works in the Roman Republic.
-
E.
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.
- 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_69ca82e6e2648190a31eaf6f4f757b2a |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:54 p.m.