Triple
T32916255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mexican–American War boundary surveys |
E842019
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States–Mexico border survey |
C61594
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: United States–Mexico border survey Context triple: [Mexican–American War boundary surveys, instanceOf, United States–Mexico border survey]
-
A.
U.S.–Mexico border crossing
A U.S.–Mexico border crossing is a designated point of entry where people, vehicles, and goods are inspected and processed as they legally move between the United States and Mexico.
-
B.
ley mexicana
Una ley mexicana es una disposición jurídica de carácter general, abstracto y obligatorio, emitida por el Congreso de la Unión o las legislaturas estatales, que regula conductas y relaciones dentro del territorio de México conforme a su Constitución.
-
C.
United States military intervention in Mexico
United States military intervention in Mexico refers to the use or deployment of U.S. armed forces within Mexican territory or against Mexican targets to influence political, economic, or security outcomes.
-
D.
Mexican pronunciamiento
A Mexican pronunciamiento is a formal, often military-led political declaration that publicly rejects the existing government or policies and calls for specific changes or a new regime.
-
E.
Border reiver
A Border reiver is a lawless raider from the Anglo-Scottish borderlands between the late Middle Ages and early 17th century, known for cattle rustling, feuding, and shifting loyalties.
- F. None of above. chosen
Provenance (1 batch)
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_69f3494779388190a5d3e97f92278be2 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:19 a.m.