Triple
T4245424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Copernicus Airport Wrocław |
E95515
|
entity |
| Predicate | operatesFlights |
P18239
|
FINISHED |
| Object | scheduled 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: scheduled flights | Statement: [Copernicus Airport Wrocław, operatesFlights, scheduled flights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesFlights Context triple: [Copernicus Airport Wrocław, operatesFlights, scheduled flights]
-
A.
operatesFlightsTo
Indicates that one entity (typically an airline) runs or provides flight services to the location represented by the other entity.
-
B.
operatesFeederFlightsFor
Indicates that one airline or carrier runs connecting or short-haul feeder flights on behalf of, or in support of, another airline’s main services.
-
C.
operatesFlightsInRegion
Indicates that an airline or carrier runs or provides flight services within a specified geographic region.
-
D.
hasTypeOfFlights
chosen
Indicates that an entity offers, includes, or is associated with specific categories or kinds of flights.
-
E.
operatedCharterFlights
Indicates that an entity conducted or managed charter flight services for another entity or purpose.
- 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_69b3453d91548190b4d4ef8fe52aa2ac |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e8db5bc8190873c5ae3753aaa58 |
completed | March 12, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69b347f587148190a1830503459939b6 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:05 p.m.