Triple

T2341767
Position Surface form Disambiguated ID Type / Status
Subject Battle of Wavre E45040 entity
Predicate campaignObjectiveFrance P15014 FINISHED
Object to prevent Prussian junction with Wellington 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: to prevent Prussian junction with Wellington | Statement: [Battle of Wavre, campaignObjectiveFrance, to prevent Prussian junction with Wellington]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: campaignObjectiveFrance
Context triple: [Battle of Wavre, campaignObjectiveFrance, to prevent Prussian junction with Wellington]
  • A. objectiveOfFrance chosen
    Indicates that something is an objective, goal, or aim pursued by France.
  • B. FrenchObjective
    Indicates that an entity serves as the goal, target, or object of an action or relation specifically within a French linguistic or contextual framework.
  • C. campaignObjectiveContext
    Indicates the specific situational or strategic context in which a campaign’s objective is defined or pursued.
  • D. goalsForFrance
    Indicates that the subject scored a goal while playing for the France national team.
  • E. countryTargeted
    Indicates that a particular country is the intended object or focus of an action, operation, or influence.
  • 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_69a88917935081909b755dbf38e81024 completed March 4, 2026, 7:33 p.m.
NER Named-entity recognition batch_69abcade3c808190ab3803538ccbe620 completed March 7, 2026, 6:51 a.m.
PD Predicate disambiguation batch_69abc59616a8819099711834e6f1ccd6 completed March 7, 2026, 6:28 a.m.
Created at: March 4, 2026, 7:52 p.m.