Triple

T32775245
Position Surface form Disambiguated ID Type / Status
Subject Quebec–New York border E838181 entity
Predicate borderSecurityType P3948 FINISHED
Object controlled but generally open for legal crossings 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: controlled but generally open for legal crossings | Statement: [Quebec–New York border, borderSecurityType, controlled but generally open for legal crossings]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: borderSecurityType
Context triple: [Quebec–New York border, borderSecurityType, controlled but generally open for legal crossings]
  • A. borderControls
    Indicates that one entity enforces or administers border control measures over another entity or at a specific boundary.
  • B. borderGuardDuty
    Indicates that an entity is assigned to perform security or monitoring duties at a border or checkpoint.
  • C. borderControlSide
    Indicates that one entity is positioned on or associated with a particular side or segment of a border control area or checkpoint.
  • D. borderRegime chosen
    Indicates the type, rules, or control system governing how movement or interaction is managed across a border between entities.
  • E. borderPostType
    Indicates the specific kind or classification of a border post associated with a boundary or crossing point.
  • 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_69f3493a824c8190938489ba69041d08 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69ff109695008190a22b47ef8be2e3f9 completed May 9, 2026, 10:46 a.m.
PD Predicate disambiguation batch_69ff0f243ea88190970d2c520b55c816 completed May 9, 2026, 10:40 a.m.
Created at: May 1, 2026, 1:13 a.m.