Triple
T24445233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reports of the Exploring Expeditions to the Rocky Mountains and to Oregon and North California |
E616384
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | exploration report |
C8416
|
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: exploration report Context triple: [Reports of the Exploring Expeditions to the Rocky Mountains and to Oregon and North California, instanceOf, exploration report]
-
A.
exploration voyage
An exploration voyage is a journey undertaken to discover, investigate, and document unknown or little-known places, phenomena, or knowledge.
-
B.
scientific expedition record
A scientific expedition record is a documented account that systematically captures the objectives, methods, observations, data, and outcomes of a specific scientific journey or field investigation.
-
C.
exploration account
chosen
An exploration account is a detailed narrative or record documenting the observations, experiences, routes, and findings made during a journey into unfamiliar or previously uncharted areas.
-
D.
colonial report
A colonial report is an official document produced by colonial authorities that details the political, economic, social, and administrative conditions of a colony for review by the imperial government or other overseeing bodies.
-
E.
explorer
An explorer is an individual who ventures into unknown or unfamiliar territories—physical, intellectual, or emotional—to discover, learn, and expand the boundaries of existing knowledge or experience.
- 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_69e2d7edca608190aafefc8877a1b4da |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 18, 2026, 2:17 a.m.