Triple

T2879929
Position Surface form Disambiguated ID Type / Status
Subject Battle of Resaca de la Palma E56970 entity
Predicate MexicanObjective P42533 FINISHED
Object push U.S. forces back from the Rio Grande 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: push U.S. forces back from the Rio Grande | Statement: [Battle of Resaca de la Palma, MexicanObjective, push U.S. forces back from the Rio Grande]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: MexicanObjective
Context triple: [Battle of Resaca de la Palma, MexicanObjective, push U.S. forces back from the Rio Grande]
  • A. strengthMexico
    Indicates a relationship where some form of strength, power, or robustness is attributed to, associated with, or exerted by Mexico.
  • B. strategicObjectiveSpain
    Indicates that an entity has a strategic objective specifically related to Spain.
  • C. isWalledCityNorthOfMexico
    Indicates that a walled city is located geographically to the north of Mexico.
  • D. borderCityOnMexicanSide
    Indicates that a city is located on the Mexican side of an international border shared with another country.
  • E. includesMexicanStatePartially
    Indicates that one entity contains some, but not all, of the territory or extent of a Mexican state.
  • F. None of above. chosen

Provenance (4 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_69ab4a4ced288190ab6d3e062d10f7f6 completed March 6, 2026, 9:42 p.m.
NER Named-entity recognition batch_69abe027beb88190ad191dba52b57454 completed March 7, 2026, 8:21 a.m.
PD Predicate disambiguation batch_69abdd15cbf08190bf7fea5ea516848a completed March 7, 2026, 8:08 a.m.
PDg Predicate description generation batch_69abdd96670c8190b727f9ac27dadf67 completed March 7, 2026, 8:11 a.m.
Created at: March 6, 2026, 10:03 p.m.