Triple
T20508340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MYNN |
E503491
|
entity |
| Predicate | USCustomsPreclearance |
P6088
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [MYNN, USCustomsPreclearance, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: USCustomsPreclearance Context triple: [MYNN, USCustomsPreclearance, yes]
-
A.
hasCustomsAndImmigration
Indicates that customs and immigration control services are present or provided at a given location or facility.
-
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.
hasUSCustomsFacilities
chosen
Indicates that a location or facility is equipped with official United States Customs services for processing people or goods entering from abroad.
-
D.
hasCustomsCheckpoint
Indicates that a location or route includes an official customs inspection point where goods, vehicles, or people are checked for compliance with border regulations.
-
E.
supportsCustomsClearance
Indicates that one entity provides or enables customs clearance services or processes for another entity or shipment.
- 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_69e0b4b1e52c8190894281cf7e3283ab |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69dc8f3c881908ed2e0257a057e73 |
completed | April 20, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69e59fdb7ad88190924176c32a195db3 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:36 a.m.