Triple
T8330728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sarcophagus of Constantine the Great |
E195066
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman imperial funerary monument |
C6381
|
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 imperial funerary monument Context triple: [Sarcophagus of Constantine the Great, instanceOf, Roman imperial funerary monument]
-
A.
ancient Roman monument
chosen
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.
Roman triumphal column
A Roman triumphal column is a monumental freestanding pillar, often spiraled with relief sculpture and topped by a statue, erected to commemorate a military victory or the achievements of an emperor.
-
C.
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.
-
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.
stone monument
A stone monument is a durable, often large-scale structure carved or assembled from stone to commemorate people, events, beliefs, or cultural values.
- 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_69ca82e87f2c8190bdb71ee29dfc642d |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:56 p.m.