Triple
T6403262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shannon Airport |
E144113
|
entity |
| Predicate | hasUSCustomsPreclearance |
P6088
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Shannon Airport, hasUSCustomsPreclearance, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUSCustomsPreclearance Context triple: [Shannon Airport, hasUSCustomsPreclearance, true]
-
A.
hasCustomsAndImmigration
Indicates that customs and immigration control services are present or provided at a given location or facility.
-
B.
supportsCustomsClearance
Indicates that one entity provides or enables customs clearance services or processes for another entity or shipment.
-
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.
hasDutyFreeArea
Indicates that one entity provides or contains a designated duty-free area for another entity or for certain activities.
-
E.
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.
- 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_69c008dc56fc81908d43ffcc11d73bdd |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c068af3f448190a94ecd5109e9e8e4 |
completed | March 22, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69c060f40ecc8190b1df17b96767675c |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:35 p.m.