Triple
T32877065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vulcan ceremonial arena |
E840956
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Vulcan cultural site |
C58543
|
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: Vulcan cultural site Context triple: [Vulcan ceremonial arena, instanceOf, Vulcan cultural site]
-
A.
Vulcan institution
A Vulcan institution is a formal organization or established system within Vulcan society that embodies and perpetuates its core values of logic, discipline, and emotional control through structured practices and governance.
-
B.
Clovis culture site
A Clovis culture site is an archaeological location in North America characterized by distinctive fluted projectile points and associated artifacts, representing some of the earliest widely distributed human occupations on the continent.
-
C.
Adena culture site
An Adena culture site is an archaeological location associated with the Adena people, characterized by burial mounds, earthworks, and related artifacts dating primarily from 1000 to 200 BCE in the Ohio Valley region.
-
D.
Haida heritage site
A Haida heritage site is a culturally significant location associated with the Haida Nation, encompassing traditional villages, sacred landscapes, archaeological remains, and places of ongoing cultural practice and identity.
-
E.
San Agustín culture site
A San Agustín culture site is an archaeological location associated with the pre-Columbian San Agustín civilization, characterized by monumental stone sculptures, burial mounds, and ceremonial architecture in the Andean region of Colombia.
- 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_69f349436ee88190b72ee12d0f3f508e |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:18 a.m.