Triple
T35163873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abu Dhabi Duty Free |
E1015339
|
entity |
| Predicate | operatesWithinFacilityType |
P2836
|
FINISHED |
| Object | international airport |
—
|
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: international airport | Statement: [Abu Dhabi Duty Free, operatesWithinFacilityType, international airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesWithinFacilityType Context triple: [Abu Dhabi Duty Free, operatesWithinFacilityType, international airport]
-
A.
usedAtFacilityType
Indicates that something is utilized or applied within a facility of a specified type.
-
B.
hasFacilityType
chosen
Indicates that an entity possesses or is associated with a specific type or category of facility.
-
C.
appliesToFacility
Indicates that something (such as a rule, policy, condition, or attribute) is relevant to, valid for, or in effect at a particular facility.
-
D.
operatesFacilitiesType
Indicates that an entity runs or manages facilities of a specified type.
-
E.
isWithinFacility
Indicates that one entity is physically located inside the boundaries or premises of a specified facility.
- 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_69f76ddbfde081908bffc91572368289 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a0127c36dc08190b07765756b3d0e1b |
completed | May 11, 2026, 12:50 a.m. |
| PD | Predicate disambiguation | batch_6a0125ef57208190be5b5e761fcae981 |
completed | May 11, 2026, 12:42 a.m. |
Created at: May 3, 2026, 4:02 p.m.