Triple

T34210676
Position Surface form Disambiguated ID Type / Status
Subject Siege of Dunkirk (1793) E877643 entity
Predicate hasReliefOperation P205366 FINISHED
Object Battle of Hondschoote E251166 NE 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: Battle of Hondschoote | Statement: [Siege of Dunkirk (1793), hasReliefOperation, Battle of Hondschoote]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasReliefOperation
Context triple: [Siege of Dunkirk (1793), hasReliefOperation, Battle of Hondschoote]
  • A. reliefOperation
    Indicates an organized effort or mission carried out to provide aid, support, or assistance in response to an emergency, crisis, or disaster.
  • B. hasRelief
    Indicates that one entity features or exhibits a raised or sculpted surface design (relief) in relation to another entity or context.
  • C. hasReliefActor
    Indicates that an entity has another entity serving as the actor responsible for providing relief or assistance in a given context.
  • D. hasReliefOf
    Indicates that one entity features, bears, or is adorned with a sculpted or carved relief representation of another entity.
  • E. hasReliefFeature
    Indicates that one entity possesses or includes a specific relief-related physical feature or characteristic.
  • F. None of above. chosen

Provenance (5 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_69f349b0b4bc819088c1552424089ee9 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_6a037c92f03c8190ae2751270b195423 completed May 12, 2026, 7:16 p.m.
NED1 Entity disambiguation (via context triple) batch_6a36e614cc6c8190b3b384224f1240f0 completed June 20, 2026, 7:12 p.m.
PD Predicate disambiguation batch_6a0379f963908190846d232f386fd98f completed May 12, 2026, 7:05 p.m.
PDg Predicate description generation batch_6a037c80ba448190853011097a151b7e completed May 12, 2026, 7:16 p.m.
Created at: May 1, 2026, 1:55 a.m.