Triple

T37683222
Position Surface form Disambiguated ID Type / Status
Subject Battle of Atapuerca E938293 entity
Predicate hasModernReenactment P72998 FINISHED
Object annual historical reenactment in Atapuerca 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: annual historical reenactment in Atapuerca | Statement: [Battle of Atapuerca, hasModernReenactment, annual historical reenactment in Atapuerca]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasModernReenactment
Context triple: [Battle of Atapuerca, hasModernReenactment, annual historical reenactment in Atapuerca]
  • A. hasReenactments chosen
    Indicates that an event, scene, or situation is represented again through staged or dramatized performances.
  • B. hasModernRevival
    Indicates that something has experienced a renewed interest, use, or popularity in modern times.
  • C. hasReenactorsFrom
    Indicates that an event, site, or activity includes or features reenactors originating from a specified place or group.
  • D. hasModernPerformances
    Indicates that the subject work or piece is currently being performed or staged in modern times.
  • E. hasModernPeriod
    Indicates that an entity possesses, is associated with, or falls within a defined modern historical or stylistic period.
  • 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_69f76ed881408190bc62a969530a4a53 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69ffada24d188190a576a02dc280a7fb completed May 9, 2026, 9:56 p.m.
PD Predicate disambiguation batch_69ffad46d6ac819081772f408b1389d5 completed May 9, 2026, 9:55 p.m.
Created at: May 3, 2026, 4:18 p.m.