Triple
T24145739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lee C. Fine Memorial Airport |
E598377
|
entity |
| Predicate | serves traffic type |
P27830
|
FINISHED |
| Object | general aviation |
—
|
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: general aviation | Statement: [Lee C. Fine Memorial Airport, serves traffic type, general aviation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serves traffic type Context triple: [Lee C. Fine Memorial Airport, serves traffic type, general aviation]
-
A.
coversTrafficType
Indicates that one entity includes, handles, or applies to a specified type or category of traffic.
-
B.
servesPassengerTrafficType
chosen
Indicates that a transportation facility or service accommodates a specified type or category of passenger traffic.
-
C.
handlesTrafficTo
Indicates that one entity is responsible for directing, managing, or routing network traffic to another entity.
-
D.
originalTrafficType
Indicates the initial category or source classification of traffic before any changes, redirects, or reattributions occur.
-
E.
trafficType
Indicates the category or nature of traffic involved in a given interaction, flow, or connection (e.g., type of network, data, or transport traffic).
- 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_69e288c9e488819093dd1acd91b08b8a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e00a37b881909e31f85a667e6d83 |
completed | April 29, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:29 p.m.