Triple
T24652282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KBIL |
E610282
|
entity |
| Predicate | hasAirTrafficControlServices |
P96239
|
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: [KBIL, hasAirTrafficControlServices, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAirTrafficControlServices Context triple: [KBIL, hasAirTrafficControlServices, yes]
-
A.
hasControlledAirspace
Indicates that a specified location or region falls within airspace where aircraft operations are regulated and managed by an aviation authority.
-
B.
providesATCServiceTo
chosen
Indicates that one entity delivers air traffic control services or support to another entity.
-
C.
hasUncontrolledAirspace
Indicates that an entity (such as a location or region) includes or is associated with airspace that is not subject to active air traffic control.
-
D.
hasAirspace
Indicates that one entity possesses, controls, or is associated with a defined region of airspace relative to another entity or area.
-
E.
hasControlTower
Indicates that one entity possesses, hosts, or is equipped with a control tower that manages or oversees its operations.
- 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_69e2c4d350a481909170482bc2ce6af9 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f41011d8048190be70329ba0bfb7c7 |
completed | May 1, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69f40ed9d47881909fcfc0d04e8d074a |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 2:34 a.m.