Triple
T35992987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anzalduas Dam |
E1040899
|
entity |
| Predicate | borderStraddlingStructureOf |
P1589
|
FINISHED |
| Object | United States–Mexico border |
—
|
NE NERFINISHED |
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: United States–Mexico border | Statement: [Anzalduas Dam, borderStraddlingStructureOf, United States–Mexico border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderStraddlingStructureOf Context triple: [Anzalduas Dam, borderStraddlingStructureOf, United States–Mexico border]
-
A.
borderStraddling
chosen
Indicates that something (such as a feature, structure, or area) extends across and occupies territory on both sides of a border between two regions or jurisdictions.
-
B.
borderSectionOf
Indicates that one entity represents a specific segment or portion of the overall border of another entity.
-
C.
borderDefinedBetween
Indicates that a boundary line or border is formally established between two geographic or political entities.
-
D.
boundaryStructure
Indicates a structural feature that serves as a physical or conceptual boundary separating or enclosing an area or object.
-
E.
borderDefinedBy
Indicates that the boundary or limit of one entity is determined, shaped, or delineated by another entity.
- 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_69f76e29084c819083987b828d414de7 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ffc516d1908190b475f5a6156b0ca8 |
completed | May 9, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69ffc4a946e08190b3535a5dc15ac484 |
completed | May 9, 2026, 11:35 p.m. |
Created at: May 3, 2026, 4:07 p.m.