Triple

T30616505
Position Surface form Disambiguated ID Type / Status
Subject Neoproterozoic Oxygenation Event E779328 entity
Predicate hasUncertainEndTime P35787 FINISHED
Object approximately between 560 and 540 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: approximately between 560 and 540 million years ago | Statement: [Neoproterozoic Oxygenation Event, hasUncertainEndTime, approximately between 560 and 540 million years ago]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasUncertainEndTime
Context triple: [Neoproterozoic Oxygenation Event, hasUncertainEndTime, approximately between 560 and 540 million years ago]
  • A. hasTemporalEnd
    Indicates that an event, state, or process concludes or terminates at a specific point or interval in time.
  • B. endTimeApproximate chosen
    Indicates that the recorded end time of an event or action is not exact but an approximate value.
  • C. hasPlannedEnding
    Indicates that an entity has a predetermined or intentionally designed conclusion or termination point.
  • D. hasUncertainty
    Indicates that the relationship or value is associated with some level or type of uncertainty rather than being fully definite or precise.
  • E. hasUncertainNumber
    Indicates that the associated quantity or count is not known precisely or cannot be determined with certainty.
  • 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_69f224a3307081909a6dca8ca75dbf48 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f7431c0eec81909ead443e07d75e18 completed May 3, 2026, 12:44 p.m.
PD Predicate disambiguation batch_69f74143cf708190a12d487884298437 completed May 3, 2026, 12:36 p.m.
Created at: April 29, 2026, 8:26 p.m.