Triple

T11640568
Position Surface form Disambiguated ID Type / Status
Subject Thornton Affair E276646 entity
Predicate partOfBroaderConflict P35813 FINISHED
Object U.S.–Mexico border disputes 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: U.S.–Mexico border disputes | Statement: [Thornton Affair, partOfBroaderConflict, U.S.–Mexico border disputes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: partOfBroaderConflict
Context triple: [Thornton Affair, partOfBroaderConflict, U.S.–Mexico border disputes]
  • A. hasPartOfConflict chosen
    Indicates that one conflict includes another conflict as a constituent or subordinate part of it.
  • B. regionOfConflict
    Indicates that a specified region is the location where a particular conflict or dispute takes place.
  • C. conflictCountry
    Indicates that there is an armed conflict or war involving the referenced country as a participant.
  • D. militaryConflict
    Indicates a relationship where two or more parties are engaged in organized, armed hostilities or warfare against each other.
  • E. politicalConflict
    Indicates a relationship where entities are engaged in opposing political positions, struggles, or disputes, often involving competition for power, influence, or policy outcomes.
  • 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_69d6aafa51148190ab84940694c00235 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a260ab488190ab1c00d9850f3096 completed April 10, 2026, 7:10 a.m.
PD Predicate disambiguation batch_69d85dd94bdc819091fa2ed33eb31624 completed April 10, 2026, 2:18 a.m.
Created at: April 8, 2026, 9:39 p.m.