Triple
T28758551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basilica of Constantine (Aula Palatina) |
E731740
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman palace basilica |
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: Roman palace basilica Context triple: [Basilica of Constantine (Aula Palatina), instanceOf, Roman palace basilica]
-
A.
Byzantine basilica
A Byzantine basilica is a Christian church building that combines the longitudinal basilican plan with characteristic Byzantine features such as domes, rich mosaics, and elaborate centralized spaces.
-
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.
Byzantine imperial palace
A Byzantine imperial palace is a grand, fortified residential and ceremonial complex that housed the emperor and court, combining administrative, religious, and domestic functions in richly decorated architectural spaces.
-
D.
ancient Roman agora
An ancient Roman agora is a central public space in a Roman city used for markets, political gatherings, social interaction, and religious activities, typically surrounded by important civic and commercial buildings.
-
E.
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.
- 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_69f043ed68a881909e858a06bab7a247 |
completed | April 28, 2026, 5:21 a.m. |
Created at: April 28, 2026, 6:10 a.m.