Triple

T19292109
Position Surface form Disambiguated ID Type / Status
Subject Plan XVII E482467 entity
Predicate didNotFullyAnticipate P51930 FINISHED
Object scale of German right-wing advance through Belgium 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: scale of German right-wing advance through Belgium | Statement: [Plan XVII, didNotFullyAnticipate, scale of German right-wing advance through Belgium]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: didNotFullyAnticipate
Context triple: [Plan XVII, didNotFullyAnticipate, scale of German right-wing advance through Belgium]
  • A. wasUnexpected chosen
    Indicates that an event, outcome, or situation occurred without prior anticipation or contrary to what was expected.
  • B. didNotBecome
    Indicates that an expected or potential change of state, role, or condition between entities did not occur.
  • C. triedToAvoid
    Indicates an entity made an effort or took action to prevent contact with, involvement in, or the occurrence of another entity or situation.
  • D. didNotLiveToSee
    Indicates that one entity died before a particular event or state involving another entity occurred, and therefore never witnessed it.
  • E. didNotHold
    Indicates that an expected event, condition, or relationship failed to occur or be valid.
  • 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_69d8e8cf61b0819096fe3e4107827c4e completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e5fc819a7881909a7afbd06d9dd3f0 completed April 20, 2026, 10:14 a.m.
PD Predicate disambiguation batch_69e4dd0bc7508190a6f9d56bd4c3404f completed April 19, 2026, 1:47 p.m.
Created at: April 10, 2026, 1:31 p.m.