Triple

T21036010
Position Surface form Disambiguated ID Type / Status
Subject Santa Cruz County, Arizona E518190 entity
Predicate hasBorderCrossing P4105 FINISHED
Object Mariposa Port of Entry NE NERFINISHED

How this triple was built (3 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: Mariposa Port of Entry | Statement: [Santa Cruz County, Arizona, hasBorderCrossing, Mariposa Port of Entry]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mariposa Port of Entry
Context triple: [Santa Cruz County, Arizona, hasBorderCrossing, Mariposa Port of Entry]
  • A. San Ysidro Port of Entry
    The San Ysidro Port of Entry is one of the busiest land border crossings in the world, connecting the United States and Mexico between San Diego and Tijuana.
  • B. Hidalgo Port of Entry
    Hidalgo Port of Entry is a major U.S.–Mexico border crossing facility in South Texas that connects the city of Hidalgo with Reynosa, Tamaulipas, supporting significant passenger and commercial traffic in the Rio Grande Valley region.
  • C. San Luis Port of Entry
    San Luis Port of Entry is a major U.S.–Mexico border crossing facility near San Luis, Arizona, that handles significant vehicular and pedestrian traffic between the two countries.
  • D. Tecate Port of Entry
    Tecate Port of Entry is a U.S.–Mexico border crossing facility connecting Tecate, California and Tecate, Baja California, serving as a smaller, less congested alternative to the main San Diego–Tijuana crossings.
  • E. Otay Mesa Port of Entry
    Otay Mesa Port of Entry is a major U.S.–Mexico border crossing in the San Diego–Tijuana region, known especially for its high volume of commercial truck traffic and cargo processing.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: Mariposa Port of Entry
Target entity description: Mariposa Port of Entry is a major U.S.–Mexico border crossing near Nogales, Arizona, serving as a key gateway for commercial truck traffic and travelers between the two countries.
  • A. San Ysidro Port of Entry
    The San Ysidro Port of Entry is one of the busiest land border crossings in the world, connecting the United States and Mexico between San Diego and Tijuana.
  • B. Hidalgo Port of Entry
    Hidalgo Port of Entry is a major U.S.–Mexico border crossing facility in South Texas that connects the city of Hidalgo with Reynosa, Tamaulipas, supporting significant passenger and commercial traffic in the Rio Grande Valley region.
  • C. San Luis Port of Entry
    San Luis Port of Entry is a major U.S.–Mexico border crossing facility near San Luis, Arizona, that handles significant vehicular and pedestrian traffic between the two countries.
  • D. Tecate Port of Entry
    Tecate Port of Entry is a U.S.–Mexico border crossing facility connecting Tecate, California and Tecate, Baja California, serving as a smaller, less congested alternative to the main San Diego–Tijuana crossings.
  • E. Otay Mesa Port of Entry
    Otay Mesa Port of Entry is a major U.S.–Mexico border crossing in the San Diego–Tijuana region, known especially for its high volume of commercial truck traffic and cargo processing.
  • F. None of above. chosen

Provenance (2 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_69e0b503275c8190afd9a163f997c709 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e6fc865ca88190abf336ee9012fa77 completed April 21, 2026, 4:26 a.m.
Created at: April 16, 2026, 2:02 p.m.