Triple

T11305374
Position Surface form Disambiguated ID Type / Status
Subject Siberian Traps large igneous province volcanism E267700 entity
Predicate beganApproximately P48368 FINISHED
Object 252 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: 252 million years ago | Statement: [Siberian Traps large igneous province volcanism, beganApproximately, 252 million years ago]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: beganApproximately
Context triple: [Siberian Traps large igneous province volcanism, beganApproximately, 252 million years ago]
  • A. began
    Indicates that one entity initiated or started an action, event, or state involving another entity or context.
  • B. beganInYear
    Indicates that an event, process, or state started in a specific calendar year.
  • C. approximateStartYear
    Indicates that the associated year value represents an estimated or imprecise starting year for an event, state, or relationship rather than an exact one.
  • D. beganWith
    Indicates that one event, process, or state started with or was initiated by another specified event, process, or state.
  • E. timeStartApprox chosen
    Indicates that the associated event or state begins at an approximate, rather than exact, point in time.
  • 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_69d6aaca5c24819083db46a30d86cb34 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e9a7255c81909675fe9ad6d71934 completed April 9, 2026, 6:02 p.m.
PD Predicate disambiguation batch_69d787aa31888190860eecaa80da5b20 completed April 9, 2026, 11:04 a.m.
Created at: April 8, 2026, 9:32 p.m.