Triple
T31055840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genex |
E791393
|
entity |
| Predicate | hasFlightNetworkBase |
P165825
|
FINISHED |
| Object | Minsk National Airport |
—
|
NE NERFINISHED |
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: [Genex, hasFlightNetworkBase, Minsk National Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFlightNetworkBase Context triple: [Genex, hasFlightNetworkBase, Minsk National Airport]
-
A.
usedByAirlineBase
chosen
Indicates that a particular airline base is utilized or operated by a specific airline.
-
B.
hasAirlines
Indicates that one entity (such as an airport, city, or country) is served by or associated with one or more airline operators.
-
C.
flightPartner
Indicates that two entities are associated as partners in operating, marketing, or coordinating a flight or set of flights.
-
D.
hasUnderlyingAirlineCallsign
Indicates that an airline-related entity is associated with a specific underlying airline callsign used for identification in air traffic communications.
-
E.
airTransportServedBy
Indicates that a particular air transport service (such as a route, flight, or airport operation) is provided or operated by a specified carrier or service provider.
- 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_69f224cb08908190ba71ad9aa87518ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 29, 2026, 9 p.m.