Triple
T26850977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turfan region |
E676056
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | archaeological site cluster |
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 site cluster Context triple: [Turfan region, instanceOf, archaeological site cluster]
-
A.
archaeological site network
An archaeological site network is a conceptual framework representing interconnected archaeological sites and their relationships through spatial, temporal, cultural, and material linkages.
-
B.
archaeological site collection
An archaeological site collection is an organized assemblage of artifacts, ecofacts, records, and related materials systematically gathered from one or more archaeological sites for study, preservation, and interpretation.
-
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 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.
-
E.
archaeological site type
An archaeological site type is a category used to classify locations of past human activity based on their physical characteristics, function, and cultural or temporal context.
- 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_69eee9b9d7708190a15d7485709ae981 |
completed | April 27, 2026, 4:44 a.m. |
Created at: April 27, 2026, 5:16 a.m.