Triple

T5605048
Position Surface form Disambiguated ID Type / Status
Subject Laurentia E147212 entity
Predicate oldestRockAge P16042 FINISHED
Object greater than 3.5 billion years 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: greater than 3.5 billion years | Statement: [Laurentia, oldestRockAge, greater than 3.5 billion years]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: oldestRockAge
Context triple: [Laurentia, oldestRockAge, greater than 3.5 billion years]
  • A. geologicalAge
    Indicates the time period in Earth's geological history during which an entity (such as a rock, fossil, or formation) originated or was formed.
  • B. estimatedAgeInMillionsOfYears chosen
    Indicates the approximate age of something expressed in units of millions of years.
  • C. hasApproximateDipOfOlderRocks
    Indicates that the dip (inclination) of older rock layers is approximately equal to a specified dip value or orientation.
  • D. oneOfTheOldestOn
    Indicates that one entity is among the earliest or longest-existing examples within the set defined by another entity.
  • E. geologicAgeRelativeTo
    Indicates the relative chronological order between two geologic ages, specifying which one is older or younger without giving an absolute date.
  • 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_69c0090500f881908374285baf0ac46f completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c020fa4b0881909fdbb8ea38eeb5e3 completed March 22, 2026, 5:03 p.m.
PD Predicate disambiguation batch_69c01b1890ec8190b9e6fa488792e4d4 completed March 22, 2026, 4:38 p.m.
Created at: March 22, 2026, 3:39 p.m.