Triple

T14093973
Position Surface form Disambiguated ID Type / Status
Subject Hia C-ed O’odham E339202 entity
Predicate borderIssues P16224 FINISHED
Object affected by U.S.–Mexico border enforcement 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: affected by U.S.–Mexico border enforcement | Statement: [Hia C-ed O’odham, borderIssues, affected by U.S.–Mexico border enforcement]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: borderIssues
Context triple: [Hia C-ed O’odham, borderIssues, affected by U.S.–Mexico border enforcement]
  • A. borderIssue
    Indicates a dispute, conflict, or problem related to the definition, control, or management of a boundary between two or more entities.
  • B. borderConcern chosen
    Indicates a relationship where one entity has issues, disputes, or security considerations related to its shared boundary or border with another entity.
  • C. borderRegime
    Indicates the type, rules, or control system governing how movement or interaction is managed across a border between entities.
  • D. borderStreet
    Indicates that a street forms or lies along the boundary between two geographic areas or properties.
  • E. borderStateAcrossInternationalBorder
    Indicates that one state shares a boundary with another state across an international border.
  • 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_69d81c69b5c8819094aa1abf18302908 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de5ee47f0881908aea8b5231b93f2f completed April 14, 2026, 3:36 p.m.
PD Predicate disambiguation batch_69de05b0e6c88190a819eeba0028981f completed April 14, 2026, 9:15 a.m.
Created at: April 9, 2026, 10:22 p.m.