Triple

T13662804
Position Surface form Disambiguated ID Type / Status
Subject Prijedor E327040 entity
Predicate hasMemorialPractices P103431 FINISHED
Object annual commemorations for war victims 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 commemorations for war victims | Statement: [Prijedor, hasMemorialPractices, annual commemorations for war victims]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMemorialPractices
Context triple: [Prijedor, hasMemorialPractices, annual commemorations for war victims]
  • A. hasMemorialPractice chosen
    Indicates that an entity engages in or is associated with a particular practice, ritual, or activity intended to commemorate or remember someone or something.
  • B. hasMemorial
    Indicates that a memorial exists in honor of, or dedicated to, a particular entity.
  • C. hasBurialCustoms
    Indicates that a group, culture, or society practices specific rituals or customs related to the treatment and burial of the dead.
  • D. hasBurialsOf
    Indicates that a location or site contains or includes the burial places of certain individuals or groups.
  • E. hasMemorialContext
    Indicates that something is related to, associated with, or situated within the context of a memorial or commemorative setting.
  • 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_69d8076d8270819092afc2f0e9c359a8 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbc622a07c81909ef7fb55e719dd9a completed April 12, 2026, 4:19 p.m.
PD Predicate disambiguation batch_69dbbe8a027081908d8f884b89707a5e completed April 12, 2026, 3:47 p.m.
Created at: April 9, 2026, 9:52 p.m.