Triple
T38193783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ZGBH |
E1005549
|
entity |
| Predicate | associatedAirportICAORegionPrefix |
—
|
GENERATED |
| Object | ZG |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedAirportICAORegionPrefix Context triple: [ZGBH, associatedAirportICAORegionPrefix, ZG]
-
A.
associatedAirportICAOSubregion
Indicates a relationship where an airport is linked to the specific ICAO-defined subregion in which it is located or with which it is operationally associated.
-
B.
hasAirportCodeRegion
Indicates that an airport code is associated with, or belongs to, a specific geographic or administrative region.
-
C.
ICAOcode
Indicates that an entity is identified by a specific four-letter airport or aerodrome code assigned by the International Civil Aviation Organization (ICAO).
-
D.
associatedAirportGeographicRegion
Indicates that an airport is located within or linked to a specific geographic region.
-
E.
hasIcaoRegion
chosen
Indicates that an entity is associated with a specific ICAO (International Civil Aviation Organization) region.
- F. None of above.
Provenance (1 batch)
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_69f76dbd22f48190940318cea061e8bb |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:29 p.m.