Triple
T495853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tijuana International Airport |
E10291
|
entity |
| Predicate | hasUSPreclearance |
P6088
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Tijuana International Airport, hasUSPreclearance, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUSPreclearance Context triple: [Tijuana International Airport, hasUSPreclearance, no]
-
A.
hasCustomsAndImmigration
Indicates that customs and immigration control services are present or provided at a given location or facility.
-
B.
hasClearanceBelow
Indicates that one entity’s clearance level is lower than another entity’s clearance level.
-
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.
visaRequirement
Indicates whether one party must obtain a visa in order to enter, stay in, or transit through the territory of another party.
-
E.
hasFreeTradeAgreement
Indicates that two entities are linked by a formal free trade agreement that reduces or eliminates trade barriers between them.
- 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_69a2e847df8481909239ec08ccf1e376 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f115334881908ac5ab96c7f4214e |
completed | Feb. 28, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_69a2edf90ca88190b6a182e5b6733612 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.