Triple

T35279812
Position Surface form Disambiguated ID Type / Status
Subject Zimbabwe–Mozambique border E1018903 entity
Predicate borderControlIncludes P36604 FINISHED
Object customs checkpoints 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: customs checkpoints | Statement: [Zimbabwe–Mozambique border, borderControlIncludes, customs checkpoints]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: borderControlIncludes
Context triple: [Zimbabwe–Mozambique border, borderControlIncludes, customs checkpoints]
  • A. borderControls chosen
    Indicates that one entity enforces or administers border control measures over another entity or at a specific boundary.
  • B. borderControlSide
    Indicates that one entity is positioned on or associated with a particular side or segment of a border control area or checkpoint.
  • C. borderControlMeasure
    Indicates a policy or action implemented to regulate, monitor, or restrict the movement of people or goods across a border.
  • D. borderControlRelevance
    Indicates the extent to which something is pertinent or applicable to border control activities, policies, or decisions.
  • E. borderControlDocument
    Indicates that a document is used or required for controlling and regulating the movement of people or goods across a 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_69f76de6d39c8190bb11342e4b91ff2b completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69ff9bed58dc8190a204816d4ed6c32c completed May 9, 2026, 8:41 p.m.
PD Predicate disambiguation batch_69ff9b69653c81908ab0d88055a66a88 completed May 9, 2026, 8:39 p.m.
Created at: May 3, 2026, 4:03 p.m.