Triple

T33194642
Position Surface form Disambiguated ID Type / Status
Subject Battle of Qarqar E849720 entity
Predicate yearInAssyrianChronology P176171 FINISHED
Object 6th regnal year of Shalmaneser III 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: 6th regnal year of Shalmaneser III | Statement: [Battle of Qarqar, yearInAssyrianChronology, 6th regnal year of Shalmaneser III]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: yearInAssyrianChronology
Context triple: [Battle of Qarqar, yearInAssyrianChronology, 6th regnal year of Shalmaneser III]
  • A. eraStartYearBC
    Indicates the year (counting backward from year 1) in which a particular era or period begins, expressed in the BC (Before Christ/BCE) dating system.
  • B. yearInRomanHistory
    Indicates that a specific year is notable or relevant within the context of Roman history.
  • C. BuddhistEraYear
    Indicates that a given year value is expressed according to the Buddhist Era (BE) calendar system rather than another calendar such as the Gregorian year.
  • D. dateFromDynasty
    Indicates that something originates from, or is associated with, a specific historical dynasty in terms of time or period.
  • E. تاريخ_الإنشاء_ميلادي
    Indicates the Gregorian calendar date on which something was created or established.
  • 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_69f3495efedc8190843a5728089544b9 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6dd3cc0648190a275812d6711275a completed May 3, 2026, 5:29 a.m.
PD Predicate disambiguation batch_69f6d82eaee081908f06a71546315aea completed May 3, 2026, 5:07 a.m.
PDg Predicate description generation batch_69f6dd3b335481909e24d4eb5b0269f9 completed May 3, 2026, 5:29 a.m.
Created at: May 1, 2026, 1:29 a.m.