Triple
T31130552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regio VII of Pompeii |
E793490
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | archaeological area |
C28428
|
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: archaeological area Context triple: [Regio VII of Pompeii, instanceOf, archaeological area]
-
A.
archaeological district
chosen
An archaeological district is a geographically defined area containing a significant concentration, linkage, or continuity of archaeological sites, features, or artifacts that collectively represent important historical or prehistorical activities or cultures.
-
B.
archaeological reserve
An archaeological reserve is a protected area designated to preserve, study, and manage archaeological sites and artifacts in situ for current and future research and education.
-
C.
archaeological locality
An archaeological locality is a specific geographic area where evidence of past human activity, such as artifacts, features, or structures, is found and studied in its environmental context.
-
D.
archaeological display site
An archaeological display site is a designated location where excavated artifacts, features, and interpretive materials are presented in situ or in a curated setting to illustrate and communicate the history and significance of an archaeological area.
-
E.
archaeological site group
An archaeological site group is a collection of spatially related archaeological sites that are interpreted together as a coherent cultural, functional, or chronological unit.
- 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_69f224d1701c819094f429798290e361 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:05 p.m.