Triple
T34127556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Vault |
E875330
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic communal burial structure |
C64538
|
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: historic communal burial structure Context triple: [Public Vault, instanceOf, historic communal burial structure]
-
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.
Bronze Age cemetery
A Bronze Age cemetery is an archaeological burial ground dating to the Bronze Age, typically containing graves, tombs, or barrows with associated artifacts that reflect the social structure, rituals, and material culture of the period.
-
C.
Scythian-era burial ground
A Scythian-era burial ground is an archaeological site containing kurgans (burial mounds) and associated grave goods that reflect the funerary practices, social hierarchy, and nomadic culture of the Scythian peoples.
-
D.
megalithic site
A megalithic site is a location featuring large stone structures or arrangements, typically constructed in prehistoric times for ceremonial, religious, or funerary purposes.
-
E.
Anglo-Saxon burial mound
An Anglo-Saxon burial mound is an earthen or stone-built barrow constructed in early medieval England to cover and mark the grave of an individual, often accompanied by grave goods and sometimes elaborate funerary structures.
- F. None of above. chosen
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_69f349aa33848190a2e6c5e4533c8444 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:53 a.m.