Triple
T36155162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irkeshtam Pass |
E1045709
|
entity |
| Predicate | customsFacility |
P7676
|
FINISHED |
| Object | Kyrgyz customs 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: Kyrgyz customs checkpoint | Statement: [Irkeshtam Pass, customsFacility, Kyrgyz customs checkpoint]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: customsFacility Context triple: [Irkeshtam Pass, customsFacility, Kyrgyz customs checkpoint]
-
A.
hasUSCustomsFacilities
Indicates that a location or facility is equipped with official United States Customs services for processing people or goods entering from abroad.
-
B.
customsClearance
Indicates the process by which goods or shipments are reviewed, processed, and officially approved by customs authorities for entry into or exit from a country.
-
C.
customs
chosen
Indicates that an entity is responsible for regulating, inspecting, or processing goods and people as they cross a border for legal and tax purposes.
-
D.
customsRegime
Indicates the specific customs treatment or regulatory framework under which goods are imported, exported, or stored.
-
E.
borderFacilityContext
Indicates a contextual relationship where an entity is associated with, operates within, or is relevant to a border facility or border-control setting.
- 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_69f76e38903c8190a52887620f90aabe |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:08 p.m.