Triple
T31611040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southwest Florida Regional Airport |
E806625
|
entity |
| Predicate | servesStateRegion |
P71989
|
FINISHED |
| Object | Florida |
—
|
NE NERFINISHED |
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: Florida | Statement: [Southwest Florida Regional Airport, servesStateRegion, Florida]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesStateRegion Context triple: [Southwest Florida Regional Airport, servesStateRegion, Florida]
-
A.
servesStateCapitalRegion
Indicates that an entity provides services or functions as a service hub for the state capital region.
-
B.
primaryStatesServed
chosen
Indicates the main geographic states that are principally served or covered by the subject.
-
C.
servesPartOfState
Indicates that an entity serves as an official or functional part of a larger state-level governmental or administrative structure.
-
D.
servesProvince
Indicates that one entity (typically an organization, service, or administrative unit) provides service or has jurisdiction over a specified province.
-
E.
servesStateOrDistrict
Indicates that an entity holds a role or position in service to a specific state or electoral district.
- 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_69f348d61f2081908cad94bc9ffbb671 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fed83b1d188190a318b0ad3003200a |
completed | May 9, 2026, 6:46 a.m. |
| PD | Predicate disambiguation | batch_69fed78e03548190b6e6ad93ae8d131d |
completed | May 9, 2026, 6:43 a.m. |
Created at: April 30, 2026, 10:36 p.m.