Triple
T32080094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belgian Flight Information Region |
E819269
|
entity |
| Predicate | trafficTypeServed |
P146573
|
FINISHED |
| Object | IFR traffic |
—
|
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: IFR traffic | Statement: [Belgian Flight Information Region, trafficTypeServed, IFR traffic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trafficTypeServed Context triple: [Belgian Flight Information Region, trafficTypeServed, IFR traffic]
-
A.
trafficServed
Indicates that a system, component, or entity handles, processes, or carries a specified amount or type of traffic (e.g., network, data, or user requests).
-
B.
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).
-
C.
coversTrafficType
chosen
Indicates that one entity includes, handles, or applies to a specified type or category of traffic.
-
D.
originalTrafficType
Indicates the initial category or source classification of traffic before any changes, redirects, or reattributions occur.
-
E.
carriedTraffic
Indicates that one entity transported, transmitted, or bore the flow of traffic (such as data, vehicles, or signals) for another entity or along a route.
- 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_69f348ff8ef88190931c08ba530a36bc |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b578cef88190bd0ceeeb17a0525f |
completed | May 3, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:24 a.m.