Triple

T8475039
Position Surface form Disambiguated ID Type / Status
Subject Prussian IV Corps E200368 entity
Predicate roleInBattleOfWaterloo P71710 FINISHED
Object arrived on the battlefield in the late afternoon 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: arrived on the battlefield in the late afternoon | Statement: [Prussian IV Corps, roleInBattleOfWaterloo, arrived on the battlefield in the late afternoon]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: roleInBattleOfWaterloo
Context triple: [Prussian IV Corps, roleInBattleOfWaterloo, arrived on the battlefield in the late afternoon]
  • A. roleAtWaterloo chosen
    Indicates the specific position, function, or capacity an entity held in relation to the Battle of Waterloo.
  • B. notableBattleRole
    Indicates the specific role or function an entity played in a notable or historically significant battle.
  • C. roleInGallicWars
    Indicates the role or involvement an entity had in the events or campaigns of the Gallic Wars.
  • D. roleInWarsOfTheRoses
    Indicates the specific part or function an entity played in the historical conflict known as the Wars of the Roses.
  • E. PrussianCommander
    Indicates that an individual holds the position or role of a commander within the Prussian military forces.
  • 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_69ca831a4f348190bfdd09250e86ae35 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cbe4f89e0081909e74beb7c8f55653 completed March 31, 2026, 3:15 p.m.
PD Predicate disambiguation batch_69cbd104250c8190b4c499dcc9937494 completed March 31, 2026, 1:49 p.m.
Created at: March 30, 2026, 6:11 p.m.