Triple
T7276263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elmira/Corning Regional Airport |
E163036
|
entity |
| Predicate | type of traffic |
P621
|
FINISHED |
| Object | commercial air service |
—
|
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: commercial air service | Statement: [Elmira/Corning Regional Airport, type of traffic, commercial air service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: type of traffic Context triple: [Elmira/Corning Regional Airport, type of traffic, commercial air service]
-
A.
trafficType
chosen
Indicates the category or nature of traffic involved in a given interaction, flow, or connection (e.g., type of network, data, or transport traffic).
-
B.
majorTrafficType
Indicates the primary kind of traffic or flow that predominantly characterizes a given route, segment, or transportation context.
-
C.
originalTrafficType
Indicates the initial category or source classification of traffic before any changes, redirects, or reattributions occur.
-
D.
hasCargoTrafficType
Indicates that an entity is associated with a specific type or category of cargo traffic it handles or supports.
-
E.
trafficDirection
Indicates the direction in which traffic is intended or allowed to move relative to a given reference point or segment.
- 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_69c6885c5964819085b209701769877f |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb8a0b4881908ff27c5a75bd4a95 |
completed | March 27, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69c6e76a84a081908d4184c55b728e48 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:59 p.m.