Triple
T7280637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hippodrome of Constantinople |
E163136
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Byzantine monument |
C21097
|
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: Byzantine monument Context triple: [Hippodrome of Constantinople, instanceOf, Byzantine monument]
-
A.
Neo-Byzantine building
A Neo-Byzantine building is a structure designed in a revival style that draws on medieval Byzantine architecture, featuring elements such as domes, rounded arches, rich ornamentation, and often elaborate brick or stonework.
-
B.
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.
-
C.
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.
-
D.
Roman-Byzantine archaeological complex
chosen
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.
-
E.
Byzantine city
A Byzantine city is an urban center of the Eastern Roman (Byzantine) Empire characterized by fortified walls, Christian religious institutions, administrative and commercial hubs, and a blend of Greco-Roman and Eastern cultural influences.
- 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_69c6885c5964819085b209701769877f |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:59 p.m.