Triple

T33265607
Position Surface form Disambiguated ID Type / Status
Subject Allied Powers in S.S. Wimbledon case E851636 entity
Predicate claimedBreachOf P177877 FINISHED
Object Treaty of Versailles by Germany NE NERFINISHED

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: Treaty of Versailles by Germany | Statement: [Allied Powers in S.S. Wimbledon case, claimedBreachOf, Treaty of Versailles by Germany]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: claimedBreachOf
Context triple: [Allied Powers in S.S. Wimbledon case, claimedBreachOf, Treaty of Versailles by Germany]
  • A. breach chosen
    Indicates that one party violates, breaks, or fails to uphold an agreed-upon obligation, rule, or boundary in relation to another.
  • B. breachedDuring
    Indicates that one entity violated, broke, or failed to uphold another entity (such as a rule, contract, or security measure) within a specified time period or event.
  • C. hasBreaches
    Indicates that one entity experiences, contains, or is affected by one or more security, structural, or policy breaches associated with another entity.
  • D. mayBeBreachBy
    Indicates that something has the potential to constitute a breach committed by a specified party.
  • E. breachedAt
    Indicates the specific time or point at which a security, contract, or boundary was violated or broken.
  • 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_69f349642dac81908a37ffcc3b976a55 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f7c29e1b848190b945c6c6120a5330 completed May 3, 2026, 9:48 p.m.
PD Predicate disambiguation batch_69f7c1b6e7a881908deb96bedb2713f4 completed May 3, 2026, 9:44 p.m.
Created at: May 1, 2026, 1:32 a.m.