Triple

T7581726
Position Surface form Disambiguated ID Type / Status
Subject Gauss–Matuyama geomagnetic reversal E179503 entity
Predicate hasApproximateTime P35787 FINISHED
Object about 2.6 million years ago LITERAL FINISHED

How this triple was built (2 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: about 2.6 million years ago | Statement: [Gauss–Matuyama geomagnetic reversal, hasApproximateTime, about 2.6 million years ago]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasApproximateTime
Context triple: [Gauss–Matuyama geomagnetic reversal, hasApproximateTime, about 2.6 million years ago]
  • A. hasApproximateDuration
    Indicates that one entity has a duration that is estimated or not exact, typically expressed as an approximate length of time.
  • B. endTimeApproximate chosen
    Indicates that the recorded end time of an event or action is not exact but an approximate value.
  • C. timeStartApprox
    Indicates that the associated event or state begins at an approximate, rather than exact, point in time.
  • D. hasApproximateEnd
    Indicates that an entity’s end point, time, or boundary is known only approximately rather than precisely.
  • E. hasApproximateValue
    Indicates that one entity’s value is close to, but not exactly equal to, the value of another entity within an acceptable margin of error.
  • F. None of above.

Provenance (3 batches)

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_69c69f327db881909a21ae3b156f8ded completed March 27, 2026, 3:16 p.m.
NER Named-entity recognition batch_69c6f978341081909e009c410ffc5039 completed March 27, 2026, 9:41 p.m.
PD Predicate disambiguation batch_69c6f4e04c2c8190a889d928515d9b8e completed March 27, 2026, 9:21 p.m.
Created at: March 27, 2026, 3:52 p.m.