Triple
T1942788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avelo Airlines |
E41591
|
entity |
| Predicate | typicalAirportType |
P16113
|
FINISHED |
| Object | secondary 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: secondary airport | Statement: [Avelo Airlines, typicalAirportType, secondary airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAirportType Context triple: [Avelo Airlines, typicalAirportType, secondary airport]
-
A.
hubAirport
Indicates that an airport serves as a primary hub or central operating base for a particular airline or carrier.
-
B.
isCivilAirport
Indicates that an airport is designated and used primarily for civilian (non-military) aviation operations.
-
C.
isPublicAirport
Indicates that an airport is open for use by the general public rather than restricted to private or military operations.
-
D.
associatedWithAirportType
chosen
Indicates that an entity has a connection or linkage to a specific category or type of airport.
-
E.
airportRole
Indicates that an entity serves a specific functional role or capacity within the context of an airport.
- 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_69a88649b24c819080047f26b6db2ded |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32ebae881908f7541301f0198ae |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abaff25a588190bb4cbc8df9fc6d64 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.