Triple
T9308770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman triumphs |
E223955
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Roman ceremony |
C1746
|
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 ceremony Context triple: [Roman triumphs, instanceOf, ancient Roman ceremony]
-
A.
event in ancient Rome
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.
ceremonial event
chosen
A ceremonial event is a formally organized occasion marked by prescribed rituals, symbols, and actions that express and reinforce cultural, social, or institutional meanings.
-
C.
ancient Roman monument
An ancient Roman monument is a large, enduring structure or commemorative work built by the Romans to honor deities, leaders, victories, or civic achievements, often showcasing advanced engineering and classical architectural styles.
-
D.
ceremonial precinct
A ceremonial precinct is a designated, often architecturally distinct area within a settlement or sacred landscape reserved for ritual, religious, or state ceremonial activities.
-
E.
ceremonial system
A ceremonial system is an organized framework of rituals, symbols, roles, and procedures that structure and regulate formal events or sacred practices within a culture or institution.
- 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_69ca8424d0f08190831e2e93c6533aeb |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:37 p.m.