Triple
T2256219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northwest Florida Regional Airport |
E49730
|
entity |
| Predicate | offersCommercialFlights |
P18239
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Northwest Florida Regional Airport, offersCommercialFlights, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersCommercialFlights Context triple: [Northwest Florida Regional Airport, offersCommercialFlights, yes]
-
A.
hasTypeOfFlights
chosen
Indicates that an entity offers, includes, or is associated with specific categories or kinds of flights.
-
B.
fareProduct
Indicates a relationship where a specific fare or price offering is associated with a particular product or service option.
-
C.
offersSearch
Indicates that one entity provides or makes available search functionality or search services to another entity.
-
D.
numberOfFlights
Indicates the total count of flights associated with a given entity or within a specified context.
-
E.
hasScheduledFlights
Indicates that there are one or more flights planned and set to occur between the related entities according to a schedule.
- 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_69a88aaa9250819095e127d0d77e8a32 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc1570dc88190bb2b17ed4c25dbb5 |
completed | March 7, 2026, 6:10 a.m. |
| PD | Predicate disambiguation | batch_69abbdb34c148190b51e99f540f97204 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.