Triple

T12741794
Position Surface form Disambiguated ID Type / Status
Subject Muktsar E304504 entity
Predicate battleCommemoratedBy P500 FINISHED
Object Gurdwaras and annual gatherings 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: Gurdwaras and annual gatherings | Statement: [Muktsar, battleCommemoratedBy, Gurdwaras and annual gatherings]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: battleCommemoratedBy
Context triple: [Muktsar, battleCommemoratedBy, Gurdwaras and annual gatherings]
  • A. commemoratedBy chosen
    Indicates that something is honored, remembered, or celebrated through a particular action, event, object, or representation.
  • B. commemoratedFor
    Indicates that one entity is honored, remembered, or celebrated because of a particular action, achievement, event, or characteristic associated with it.
  • C. commemoratedIn
    Indicates that something is honored, remembered, or recognized within a particular work, event, place, or medium.
  • D. regionOfBattlesCommemorated
    Indicates the geographic region where the battles being commemorated took place.
  • E. commemoratesConflict
    Indicates a relationship where something (such as a monument, event, or work) serves to remember, honor, or mark a specific conflict or war.
  • 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_69d7bdf1426c8190a4402e1c4cdec33a completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d96d89ea70819098c470344f172167 completed April 10, 2026, 9:37 p.m.
PD Predicate disambiguation batch_69d96406e97c8190b79081039847115c completed April 10, 2026, 8:56 p.m.
Created at: April 9, 2026, 5:26 p.m.