Triple
T31217147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UMMM |
E795899
|
entity |
| Predicate | relatedAirport |
—
|
GENERATED |
| Object | Minsk National Airport |
—
|
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: relatedAirport Context triple: [UMMM, relatedAirport, Minsk National Airport]
-
A.
associatedAirport
chosen
Indicates a relationship where an entity is linked or connected to a specific airport, typically as its relevant or corresponding airport.
-
B.
associatedAirportServes
Indicates that a given airport provides service to, or is used by, the associated entity (such as a city, region, or facility).
-
C.
associatedHubAirport
Indicates that one entity serves as a primary or hub airport functionally linked to the other entity.
-
D.
associatedAirportReplaced
Indicates that one airport in an association has been superseded or replaced by another airport.
-
E.
relatedAirfield
Indicates that there is an association or connection between an entity and a specific airfield, such as operational use, location, or administrative linkage.
- 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_69f224d9d52c8190a61f68ded37fa755 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:10 p.m.