Triple
T35095411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japanese–Peruvian archaeological missions |
E1012853
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | archaeological research collaboration |
C34225
|
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 research collaboration Context triple: [Japanese–Peruvian archaeological missions, instanceOf, archaeological research collaboration]
-
A.
archaeological partnership
chosen
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.
-
B.
archaeological study
An archaeological study is a systematic investigation of past human cultures through the recovery, analysis, and interpretation of material remains and environmental data.
-
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 society
An archaeological society is an organized group dedicated to the study, preservation, and public understanding of past human cultures through the investigation and interpretation of material remains.
-
E.
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.
- 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_69f76dd432ec8190969bc32acfc152b1 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.