Triple

T25463084
Position Surface form Disambiguated ID Type / Status
Subject Amazigh calendar E638102 entity
Predicate eraStartYearBC P158847 FINISHED
Object 950 BC 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: 950 BC | Statement: [Amazigh calendar, eraStartYearBC, 950 BC]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: eraStartYearBC
Context triple: [Amazigh calendar, eraStartYearBC, 950 BC]
  • A. approximateStartCenturyBC
    Indicates that an entity’s starting time or occurrence is approximately located within a specified century before the Common Era (BC).
  • B. approximateEndCenturyBCE_CE
    Indicates that an event or entity is estimated to have ended in a particular century, which may be expressed in either BCE or CE.
  • C. approximateBirthCenturyBCE
    Indicates that an entity’s birth is estimated to have occurred within a specified century before the Common Era (BCE), rather than on an exact year or date.
  • D. approximateCenturyBC
    Indicates that something occurred or existed around a specified century before the start of the Common Era, with the time given as an approximate rather than exact century.
  • E. approximateUseEndCenturyBC
    Indicates an estimated century BCE by which the use or activity associated with the subject is believed to have ended.
  • F. None of above. chosen

Provenance (4 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_69e75db8bab08190baca80b4a8c315fd completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f5f72dd1788190a5a74326054e6822 completed May 2, 2026, 1:07 p.m.
PD Predicate disambiguation batch_69f480789be08190ab252a6de3797200 completed May 1, 2026, 10:29 a.m.
PDg Predicate description generation batch_69f48b9058d081908ec9af261ee092e2 completed May 1, 2026, 11:16 a.m.
Created at: April 21, 2026, 2:13 p.m.