Triple

T2690552
Position Surface form Disambiguated ID Type / Status
Subject Battle of Monterrey E57589 entity
Predicate hasSurrender P29098 FINISHED
Object Mexican garrison of Monterrey surrendered to U.S. forces 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: Mexican garrison of Monterrey surrendered to U.S. forces | Statement: [Battle of Monterrey, hasSurrender, Mexican garrison of Monterrey surrendered to U.S. forces]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSurrender
Context triple: [Battle of Monterrey, hasSurrender, Mexican garrison of Monterrey surrendered to U.S. forces]
  • A. surrenderEvent
    Indicates an event in which one party yields or gives up control, rights, or resistance to another party.
  • B. surrenderedIn chosen
    Indicates that an entity yielded or gave up control, power, or resistance within a specific event, context, or situation.
  • C. surrenderingParty
    Indicates the party that yields control, rights, or possession to another in a surrender or transfer arrangement.
  • D. loserStatus
    Indicates that an entity has been judged or designated as the loser in a particular comparison, contest, or evaluative context.
  • E. surrenderDate
    Indicates the date on which an entity formally yields control, possession, or rights, typically ending its claim or resistance.
  • 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_69ab4a5028388190a36f3baf1588309e completed March 6, 2026, 9:42 p.m.
NER Named-entity recognition batch_69abda0ba2208190ad87763ecbef8c3c completed March 7, 2026, 7:55 a.m.
PD Predicate disambiguation batch_69abd81c9b4c81908e5e0da6ac5f828b completed March 7, 2026, 7:47 a.m.
Created at: March 6, 2026, 9:54 p.m.