Triple

T9749945
Position Surface form Disambiguated ID Type / Status
Subject World War II Battle of Cherbourg E236414 entity
Predicate garrisonSurrender P83797 FINISHED
Object German garrison at Cherbourg surrendered to U.S. 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: German garrison at Cherbourg surrendered to U.S. forces | Statement: [World War II Battle of Cherbourg, garrisonSurrender, German garrison at Cherbourg surrendered to U.S. forces]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: garrisonSurrender
Context triple: [World War II Battle of Cherbourg, garrisonSurrender, German garrison at Cherbourg surrendered to U.S. forces]
  • A. garrisonSurrenderedTo chosen
    Indicates that a defending military garrison formally capitulated and yielded control to another party.
  • B. placeOfSurrender
    Indicates the location where an entity formally surrendered to another party.
  • C. surrenderedIn
    Indicates that an entity yielded or gave up control, power, or resistance within a specific event, context, or situation.
  • D. surrenderedAfter
    Indicates that one entity surrendered following or as a consequence of another specified event, action, or time.
  • E. garrisonAttacked
    Indicates that a military garrison was subjected to an attack by another force or entity.
  • 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_69ca84d4eddc8190996fec1417d2bae8 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cd9f6a2f8c8190a6f6af6587ee90b8 completed April 1, 2026, 10:42 p.m.
PD Predicate disambiguation batch_69cd03cc128c81908b84ef224f858b4e completed April 1, 2026, 11:38 a.m.
Created at: March 30, 2026, 8:24 p.m.