Triple
T1143550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Theatre of Orange |
E23511
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Roman theatre |
C2879
|
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 theatre Context triple: [Roman Theatre of Orange, instanceOf, ancient Roman theatre]
-
A.
Roman theatre
chosen
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.
-
B.
amphitheater
An amphitheater is an open or semi-open circular or oval venue with tiered seating surrounding a central performance area, designed to host public events, performances, or gatherings.
-
C.
ancient Greek theatre
Ancient Greek theatre is a classical performance tradition combining drama, music, and dance in large open-air amphitheaters, used for religious festivals, civic engagement, and storytelling through tragedy, comedy, and satyr plays.
-
D.
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.
-
E.
ancient Greek stadium
An ancient Greek stadium is a large, elongated open-air structure with tiered seating, designed primarily for athletic competitions such as footraces and other events of the Panhellenic games.
- 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_69a493ef399c8190b04b9146d2314f59 |
completed | March 1, 2026, 7:30 p.m. |
Created at: March 1, 2026, 7:44 p.m.