Triple
T33564889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Société d’histoire et d’archéologie de Genève |
E859729
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | archaeological society |
C60916
|
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 society Context triple: [Société d’histoire et d’archéologie de Genève, instanceOf, archaeological society]
-
A.
archaeology journal
An archaeology journal is a periodical publication that presents scholarly research, findings, and discussions related to the study of past human cultures through material remains.
-
B.
archaeology agency
An archaeology agency is an organization that conducts, manages, and oversees archaeological research, excavations, and heritage preservation projects, often coordinating with governments, developers, and academic institutions.
-
C.
archaeological research institute
An archaeological research institute is an organization dedicated to the systematic study, excavation, analysis, and preservation of material remains from past human cultures to advance historical and scientific knowledge.
-
D.
archaeological partnership
An archaeological partnership is a collaborative relationship between individuals, institutions, or communities that jointly plan, conduct, and interpret archaeological research while sharing resources, responsibilities, and benefits.
-
E.
archaeology department
An archaeology department is an academic unit dedicated to the systematic study, research, and teaching of past human cultures through the analysis of material remains and related scientific methods.
- 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_69f3497c1d288190a844ea699914e038 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:40 a.m.