Triple
T4416063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arlington Springs Man site |
E94976
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | prehistoric human remains site |
C7589
|
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: prehistoric human remains site Context triple: [Arlington Springs Man site, instanceOf, prehistoric human remains site]
-
A.
paleoanthropological site
chosen
A paleoanthropological site is a location where physical evidence of ancient humans and their ancestors—such as fossils, artifacts, and environmental remains—is preserved and studied to understand human evolution.
-
B.
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.
-
C.
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.
-
D.
reconstructed historic site
A reconstructed historic site is a place where buildings, structures, or environments from the past have been rebuilt or significantly restored to approximate their original appearance and context for educational, commemorative, or touristic purposes.
-
E.
nuragic archaeological site
A nuragic archaeological site is a prehistoric complex in Sardinia characterized by stone towers (nuraghi), villages, tombs, and ritual structures built by the Nuragic civilization between the Bronze and Iron Ages.
- 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_69b34539638c8190abfea3eb29425210 |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:29 p.m.