Triple
T21170679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orion correlation theory |
E521682
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | pseudoarchaeological theory |
C26689
|
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: pseudoarchaeological theory Context triple: [Orion correlation theory, instanceOf, pseudoarchaeological theory]
-
A.
pseudoarchaeology literature
Pseudoarchaeology literature consists of books and writings that present speculative, unscientific, or debunked interpretations of archaeological evidence, often emphasizing sensational claims about ancient civilizations, lost technologies, or extraterrestrial influences.
-
B.
speculative theory
chosen
A speculative theory is a conceptual framework or explanation proposed to account for phenomena based on limited evidence, emphasizing conjecture and possibility rather than established empirical validation.
-
C.
debunker of pseudoscience
A debunker of pseudoscience critically investigates and exposes false or unsubstantiated scientific claims using evidence-based reasoning and clear communication.
-
D.
archaeological phenomenon
An archaeological phenomenon is a recurring pattern, feature, or assemblage identified in the archaeological record that reflects specific past human activities, behaviors, or cultural processes.
-
E.
archaeological narrative
An archaeological narrative is a structured account that interprets and weaves together material remains, contextual data, and theoretical perspectives to reconstruct and explain past human activities and cultures.
- 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_69e0b50e30748190b186824a206d39b9 |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 3 p.m.