Triple
T26818403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gauss normal chron |
E675178
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | geomagnetic polarity chron |
C6731
|
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: geomagnetic polarity chron Context triple: [Gauss normal chron, instanceOf, geomagnetic polarity chron]
-
A.
geomagnetic pole
A geomagnetic pole is one of the two points on the Earth's surface where the axis of its internal magnetic field, approximated as a dipole, intersects the planet, indicating the theoretical locations of maximum magnetic field inclination.
-
B.
geologic time scale
The geologic time scale is a chronological framework that organizes Earth's 4.6-billion-year history into eons, eras, periods, epochs, and ages based on major geological and biological events.
-
C.
chronostratigraphic chart
A chronostratigraphic chart is a diagram that organizes rock layers and geological events in chronological order to illustrate the relative timing and duration of Earth’s stratigraphic units.
-
D.
chronostratigraphic reference point
A chronostratigraphic reference point is a precisely defined boundary in geological time, often marked by a Global Boundary Stratotype Section and Point (GSSP), used to correlate and standardize rock layers and time intervals worldwide.
-
E.
geologic time interval
chosen
A geologic time interval is a span of Earth’s history defined by characteristic rock layers, fossil assemblages, and major geological or biological events, used to organize and correlate geological and paleontological data.
- 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_69eee9b6b28481909332f83eb17e5170 |
completed | April 27, 2026, 4:44 a.m. |
Created at: April 27, 2026, 4:53 a.m.