Triple

T27761891
Position Surface form Disambiguated ID Type / Status
Subject Battle of the Metaxas Line E701490 entity
Predicate tacticUsedByGermany P108400 FINISHED
Object flanking maneuver through Yugoslav territory 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: flanking maneuver through Yugoslav territory | Statement: [Battle of the Metaxas Line, tacticUsedByGermany, flanking maneuver through Yugoslav territory]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: tacticUsedByGermany
Context triple: [Battle of the Metaxas Line, tacticUsedByGermany, flanking maneuver through Yugoslav territory]
  • A. strategyUsedByGermany chosen
    Indicates that a particular strategy is one that was employed or adopted by Germany.
  • B. aimOfGermanForces
    Indicates that the specified objective or target is the intended goal or purpose of the actions undertaken by German military forces.
  • C. GermanLoss
    Indicates that Germany experiences a loss, defeat, or negative outcome in the specified context or event.
  • D. combatantRoleOfGermany
    Indicates that the specified role is one that Germany held as a combatant in a particular conflict or war.
  • E. objectiveGermany
    Indicates that an entity has Germany as its objective, target, or goal in a given context.
  • 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_69ef6a5193808190816eb7d0020b2d87 completed April 27, 2026, 1:53 p.m.
NER Named-entity recognition batch_69f63fd6c68481908c542aa03e297b9c completed May 2, 2026, 6:17 p.m.
PD Predicate disambiguation batch_69f63c6895f0819088655277e45859a8 completed May 2, 2026, 6:03 p.m.
Created at: April 27, 2026, 4:27 p.m.