Triple
T31217147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UMMM |
E795899
|
entity |
| Predicate | relatedAirport |
P58803
|
FINISHED |
| Object | Minsk National Airport |
E224069
|
NE 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: Minsk National Airport | Statement: [UMMM, relatedAirport, Minsk National Airport]
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 (4 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_69f224d9d52c8190a61f68ded37fa755 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2eb11af7a48190b9e318a0d4ea2dad |
completed | June 14, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9:10 p.m.