Triple
T172544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phoenix Sky Harbor International Airport |
E3506
|
entity |
| Predicate | hasUSCustomsFacilities |
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: [Phoenix Sky Harbor International Airport, hasUSCustomsFacilities, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUSCustomsFacilities Context triple: [Phoenix Sky Harbor International Airport, hasUSCustomsFacilities, yes]
-
A.
customsRegime
Indicates the specific customs treatment or regulatory framework under which goods are imported, exported, or stored.
-
B.
hasCargoTerminal
Indicates that a location or facility includes or is equipped with a cargo terminal for handling freight.
-
C.
hasBorderCrossing
Indicates that there exists a point or facility where movement or transit is possible between the boundaries of two adjacent regions or jurisdictions.
-
D.
hasUNLocode
Indicates that an entity is associated with a specific UN/LOCODE, identifying its location in the United Nations location code system.
-
E.
hasInternationalAirport
Indicates that a place possesses an airport that handles international flights and services cross-border air traffic.
- F. None of above. chosen
Provenance (4 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_69a25374990081909766d30c79a18e0e |
completed | Feb. 28, 2026, 2:31 a.m. |
| NER | Named-entity recognition | batch_69a258e0b11c8190b7b5cf3c354c47ce |
completed | Feb. 28, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69a256689f908190afeb5ee82022a911 |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a25737f9188190b9690dce98aed83a |
completed | Feb. 28, 2026, 2:47 a.m. |
Created at: Feb. 28, 2026, 2:39 a.m.