Triple
T8352533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Early Christian Necropolis of Pécs (Sopianae) |
E196596
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman necropolis |
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 necropolis Context triple: [Early Christian Necropolis of Pécs (Sopianae), instanceOf, Roman necropolis]
-
A.
prehistoric underground burial complex
A prehistoric underground burial complex is a network of subterranean chambers and passages constructed by ancient societies to inter the dead, often accompanied by ritual artifacts and symbolic architecture.
-
B.
New Kingdom burial complex
A New Kingdom burial complex is an architecturally elaborate mortuary installation—often including tombs, chapels, shafts, and associated cult spaces—designed to house and ritually sustain the dead within the religious and political landscape of New Kingdom Egypt.
-
C.
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.
-
D.
mausoleum
A mausoleum is a free-standing, often monumental building constructed as a tomb to house and honor the dead.
-
E.
tomb
A tomb is a structure or chamber, often built of stone or underground, designed to house and commemorate the dead and their remains.
- 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_69ca82f08b348190bfb7881944bbff6f |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:59 p.m.