Triple
T28218489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pardubice Airport |
E711383
|
entity |
| Predicate | hasCivilOperator |
P57533
|
FINISHED |
| Object | East Bohemian Airport a.s. |
—
|
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: East Bohemian Airport a.s. | Statement: [Pardubice Airport, hasCivilOperator, East Bohemian Airport a.s.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCivilOperator Context triple: [Pardubice Airport, hasCivilOperator, East Bohemian Airport a.s.]
-
A.
civilOperator
chosen
Indicates that an entity performs or is responsible for operating a civil (non-military) system, service, or infrastructure.
-
B.
hasOperatorJurisdiction
Indicates that a particular operator has official authority or control over a specified entity, area, or operation.
-
C.
hasCampOperator
Indicates that a camp is operated or managed by a specific operator or organization.
-
D.
hasOperatorContractAuthority
Indicates that an entity has the legal or formal authority to enter into and manage operator contracts on behalf of another party or organization.
-
E.
hasOperatorContractStart
Indicates the date on which an operator’s contractual agreement with another entity begins.
- 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_69efb51cb5288190818c1f63a266af11 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 27, 2026, 10:45 p.m.