Triple
T12937834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lugdunum Museum and Roman Theatres |
E309559
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Roman theatre complex |
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 complex Context triple: [Lugdunum Museum and Roman Theatres, instanceOf, ancient Roman theatre complex]
-
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.
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-Byzantine archaeological complex
A Roman-Byzantine archaeological complex is an integrated site containing architectural remains, artifacts, and stratified layers that document the transition and continuity between Roman and Byzantine periods in a specific region.
-
D.
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.
-
E.
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.
- 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_69d7bdfa933c8190b5a27aa4a08a19b7 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:43 p.m.