Triple
T33276186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puuc Route |
E851912
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | archaeological circuit |
C10940
|
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 circuit Context triple: [Puuc Route, instanceOf, archaeological circuit]
-
A.
archaeological site network
chosen
An archaeological site network is a conceptual framework representing interconnected archaeological sites and their relationships through spatial, temporal, cultural, and material linkages.
-
B.
archaeological component
An archaeological component is a distinct, temporally and functionally coherent set of artifacts, features, and other cultural materials at a site that represents a specific episode or phase of past human activity.
-
C.
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.
-
D.
archaeological culture
An archaeological culture is a recurring assemblage of artifacts, features, and other material remains that archaeologists interpret as representing the activities and shared practices of a particular group of people in a specific time and place.
-
E.
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.
- 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_69f349653da08190819876015a298fdb |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:32 a.m.