Triple
T4083076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ted Stevens Anchorage International Airport |
E87522
|
entity |
| Predicate | isPassengerGateway |
P45777
|
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: [Ted Stevens Anchorage International Airport, isPassengerGateway, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPassengerGateway Context triple: [Ted Stevens Anchorage International Airport, isPassengerGateway, true]
-
A.
hasPassengerRole
Indicates that an entity participates in a context or event specifically in the capacity or role of a passenger.
-
B.
isPassengerStationCode
Indicates that a given code is officially assigned to identify a particular passenger station.
-
C.
hasPassengerUsageCategory
Indicates the classification of how a passenger-related resource or service is used (e.g., its usage type or category for passengers).
-
D.
hasPassengerTerminalFunction
chosen
Indicates that something serves the role or performs the function of a passenger terminal, supporting the handling and movement of passengers.
-
E.
passengerAccess
Indicates that a passenger is allowed to enter, use, or move through a particular vehicle, area, or transportation-related 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_69aed9435cf48190ad1da737c962d19d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefc7933b481909bb3e02c6c04c8ee |
completed | March 9, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69aef9082c2081908474f082a49bebc8 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:39 p.m.