Triple
T36591720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Durango International Airport |
E902686
|
entity |
| Predicate | hasBaggageFacilities |
P30952
|
FINISHED |
| Object | baggage claim area |
—
|
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: baggage claim area | Statement: [Durango International Airport, hasBaggageFacilities, baggage claim area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBaggageFacilities Context triple: [Durango International Airport, hasBaggageFacilities, baggage claim area]
-
A.
hasBaggageService
Indicates that an entity provides or supports services related to handling, storing, or managing baggage for others.
-
B.
hasBaggageSystem
Indicates that an entity is equipped with or utilizes a baggage handling system.
-
C.
hasPassengerAmenity
Indicates that an entity provides or is equipped with a specific amenity intended for the comfort or convenience of its passengers.
-
D.
hasBaggageClaim
chosen
Indicates that a location, typically a transportation hub, includes or provides a baggage claim area for retrieving luggage.
-
E.
hasOnboardLuggageSpace
Indicates that an entity provides or includes dedicated space for carrying luggage on board.
- 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_69f76e6592e88190bac4eb00a46e9df9 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd864235b481908738dbb69556bc62 |
completed | May 8, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69fd8373b6bc819091c554f29ee17fec |
completed | May 8, 2026, 6:32 a.m. |
Created at: May 3, 2026, 4:11 p.m.