Triple
T18700306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hayden Survey party |
E457231
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | geological survey expedition |
C10858
|
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: geological survey expedition Context triple: [Hayden Survey party, instanceOf, geological survey expedition]
-
A.
geological survey
chosen
A geological survey is a systematic investigation and mapping of the Earth's materials, structures, and processes to understand subsurface conditions and support resource management, hazard assessment, and land-use planning.
-
B.
archaeological expedition
An archaeological expedition is a planned scientific journey undertaken by researchers to locate, excavate, and analyze material remains of past human cultures at specific sites.
-
C.
IODP expedition
An IODP expedition is a scientific research voyage conducted under the International Ocean Discovery Program to drill, sample, and analyze subseafloor sediments and rocks in order to study Earth’s history, structure, and processes.
-
D.
geological survey organization
A geological survey organization is an institution that systematically investigates, maps, analyzes, and monitors the Earth’s materials, structures, and processes to support resource management, hazard assessment, and scientific understanding.
-
E.
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.
- 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_69d8d392aad081909fe31aa03e6e97d1 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:49 a.m.