Triple
T3608340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pisonian conspiracy |
E76426
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in ancient Rome |
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: event in ancient Rome Context triple: [Pisonian conspiracy, instanceOf, event in ancient Rome]
-
A.
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.
-
B.
ancient Roman structure
An ancient Roman structure is a man-made construction from the Roman civilization, such as temples, amphitheaters, aqueducts, or baths, characterized by advanced engineering, arches, and durable materials like stone and concrete.
-
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.
phase of the Roman Empire
A phase of the Roman Empire is a distinct historical period characterized by specific political structures, territorial extents, social dynamics, and cultural developments within the broader continuum of Roman rule.
-
E.
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.
- 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_69ad85da0ba481908b3b48c69efe2b98 |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:22 p.m.