Triple
T36512326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akutan Airport |
E899939
|
entity |
| Predicate | hasAirServiceType |
P121552
|
FINISHED |
| Object | regional commuter flights |
—
|
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: regional commuter flights | Statement: [Akutan Airport, hasAirServiceType, regional commuter flights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAirServiceType Context triple: [Akutan Airport, hasAirServiceType, regional commuter flights]
-
A.
airServiceType
chosen
Indicates the specific category or nature of an air transportation service provided or used in the relationship.
-
B.
servesAviationType
Indicates that one entity provides services or functions specifically for a particular type or category of aviation.
-
C.
hasPassengerAirlineService
Indicates that a location or facility is served by scheduled passenger airline flights.
-
D.
servesAirlineType
Indicates that a service provider (such as an airport, terminal, or facility) accommodates or operates flights for a specified type or category of airline.
-
E.
hasPassengerServicesType
Indicates the type or category of passenger services that are provided or associated with an entity.
- 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_69f76e5dada881909da2d34bc7a9202a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:10 p.m.