Triple
T8448845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gamzigrad (Felix Romuliana) |
E199749
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Roman imperial palace |
C9633
|
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 imperial palace Context triple: [Gamzigrad (Felix Romuliana), instanceOf, ancient Roman imperial palace]
-
A.
Roman imperial residence
chosen
A Roman imperial residence is a grand, often fortified palace complex that served as the official home, administrative center, and ceremonial stage for the Roman emperor and his court.
-
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.
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 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.
-
E.
imperial forum
An imperial forum is a monumental public complex in ancient Roman cities, commissioned by emperors to serve as a political, religious, and commercial center adorned with grand architecture and statuary.
- 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_69ca83170f9081909cd98f55614c6476 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:09 p.m.