Triple
T3674325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poznań–Ławica Airport |
E77952
|
entity |
| Predicate | offersFlightType |
P18239
|
FINISHED |
| Object | domestic flights |
—
|
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: domestic flights | Statement: [Poznań–Ławica Airport, offersFlightType, domestic flights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersFlightType Context triple: [Poznań–Ławica Airport, offersFlightType, domestic flights]
-
A.
hasTypeOfFlights
chosen
Indicates that an entity offers, includes, or is associated with specific categories or kinds of flights.
-
B.
offersClassOfTravel
Indicates that a service provider makes a particular class or tier of travel (e.g., economy, business, first) available as an option.
-
C.
fareProduct
Indicates a relationship where a specific fare or price offering is associated with a particular product or service option.
-
D.
servesAirlineType
Indicates that a service provider (such as an airport, terminal, or facility) accommodates or operates flights for a specified type or category of airline.
-
E.
offersPlanType
Indicates that one entity provides or makes available a specific type of plan to another entity or in a given context.
- 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_69ad85e083008190b2e1b7085fe500bd |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc45fbd1c819099023791452f1beb |
completed | March 8, 2026, 6:47 p.m. |
| PD | Predicate disambiguation | batch_69adb84a20288190a092e4a1b045fe3f |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:25 p.m.