Triple

T19568681
Position Surface form Disambiguated ID Type / Status
Subject Battle of Fredericia E489652 entity
Predicate siegeStatusBefore P73538 FINISHED
Object Fredericia under siege by Schleswig-Holstein forces 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: Fredericia under siege by Schleswig-Holstein forces | Statement: [Battle of Fredericia, siegeStatusBefore, Fredericia under siege by Schleswig-Holstein forces]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: siegeStatusBefore
Context triple: [Battle of Fredericia, siegeStatusBefore, Fredericia under siege by Schleswig-Holstein forces]
  • A. cityStatusDuringSiege
    Indicates the condition or status of a city specifically during the period in which it is under siege.
  • B. statusOfCityBeforeBattle chosen
    Indicates the condition or situation a city was in immediately prior to a specific battle.
  • C. siegeOccurredIn
    Indicates that a siege took place within or at the location specified by the related entity.
  • D. sieged
    Indicates that one entity has surrounded and blockaded another entity or location, typically to cut off supplies and force surrender.
  • E. siegeRelated
    Indicates a relationship in which one entity is involved with, associated with, or relevant to a siege or siege-related activities.
  • 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_69d8e8dd9374819098e36349b3211663 completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e63f79adf08190b1c0b008f30b0acd completed April 20, 2026, 3 p.m.
PD Predicate disambiguation batch_69e514d4df3c8190b7e9b3b4fdf9452a completed April 19, 2026, 5:45 p.m.
Created at: April 10, 2026, 1:42 p.m.