Triple
T16719952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Geophysical Year activities |
E406321
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | geophysical research campaign |
C37803
|
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: geophysical research campaign Context triple: [International Geophysical Year activities, instanceOf, geophysical research campaign]
-
A.
seismological project
A seismological project is an organized scientific effort that designs and conducts studies to measure, analyze, and interpret seismic activity and Earth’s subsurface structures.
-
B.
seismological experiment
A seismological experiment is a systematic investigation that uses controlled or natural seismic sources and sensor networks to measure, analyze, and interpret ground motions to understand Earth's structure and seismic processes.
-
C.
airborne geophysical survey
An airborne geophysical survey is a method of collecting geophysical data about the Earth's subsurface from aircraft or drones using instruments that measure variations in properties such as magnetism, gravity, and electromagnetic response.
-
D.
scientific drilling project
A scientific drilling project is a coordinated research effort that uses specialized drilling techniques to recover subsurface samples and data in order to investigate geological, environmental, or planetary processes.
-
E.
geological mapping program
A geological mapping program is a software tool that enables users to collect, analyze, and visualize spatial geological data to create detailed maps of rock types, structures, and other earth features.
- 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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:20 a.m.