Triple
T28708643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zentralanstalt für Meteorologie und Geodynamik |
E729766
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | geophysical service |
C55192
|
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 service Context triple: [Zentralanstalt für Meteorologie und Geodynamik, instanceOf, geophysical service]
-
A.
geophysical engineering department
A geophysical engineering department is an academic and research unit focused on applying physics-based methods to study and solve problems related to the Earth's subsurface, natural resources, and geohazards.
-
B.
geodetic service organization
A geodetic service organization is an entity that plans, conducts, and manages geodetic measurements and analyses to provide accurate reference frames, positioning data, and related geospatial services.
-
C.
geological survey
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.
-
D.
geophysical model
A geophysical model is a mathematical or computational representation of Earth's physical properties and processes used to simulate, interpret, and predict geologic and geodynamic phenomena.
-
E.
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.
- 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_69f043e7d5a4819094b18aca10b1e024 |
completed | April 28, 2026, 5:21 a.m. |
Created at: April 28, 2026, 5:46 a.m.