Triple

T7676992
Position Surface form Disambiguated ID Type / Status
Subject Mae Sai E173886 entity
Predicate borderCheckpointType P47626 FINISHED
Object international land border checkpoint 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: international land border checkpoint | Statement: [Mae Sai, borderCheckpointType, international land border checkpoint]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: borderCheckpointType
Context triple: [Mae Sai, borderCheckpointType, international land border checkpoint]
  • A. borderPostType chosen
    Indicates the specific kind or classification of a border post associated with a boundary or crossing point.
  • B. borderStation
    Indicates a facility or checkpoint located at or near a border where cross-boundary movement, control, or processing of people or goods occurs.
  • C. borderControls
    Indicates that one entity enforces or administers border control measures over another entity or at a specific boundary.
  • D. borderPostName
    Indicates the specific name assigned to a border post where a boundary crossing or checkpoint is located.
  • E. borderControlSide
    Indicates that one entity is positioned on or associated with a particular side or segment of a border control area or checkpoint.
  • 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_69c6995703e0819081de77361b602e78 completed March 27, 2026, 2:51 p.m.
NER Named-entity recognition batch_69c7048b0b448190889bd40e0a38e51a completed March 27, 2026, 10:28 p.m.
PD Predicate disambiguation batch_69c701618d3481908be84b76f36ac5a1 completed March 27, 2026, 10:14 p.m.
Created at: March 27, 2026, 4:01 p.m.