Triple
T9020860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ostend–Bruges International Airport |
E215716
|
entity |
| Predicate | servesCargoOperators |
P11980
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Ostend–Bruges International Airport, servesCargoOperators, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesCargoOperators Context triple: [Ostend–Bruges International Airport, servesCargoOperators, yes]
-
A.
hasCargoServices
chosen
Indicates that an entity provides or is equipped to handle cargo transportation or freight services for another entity or location.
-
B.
primaryCargoOperator
Indicates that an entity serves as the main organization responsible for operating or managing the cargo-related activities of another entity.
-
C.
servesAsCargoHubFor
Indicates that one entity functions as a central location or facility for handling, consolidating, and distributing cargo associated with another entity.
-
D.
mainCargo
Indicates that one entity serves as the primary or principal cargo carried or transported by another entity.
-
E.
logisticsSupportFrom
Indicates that one entity provides logistical assistance, resources, or services to another entity.
- 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_69ca83a38aa88190bf1bb80c4548b5e2 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a43add08190983b7ac88576fd7e |
completed | April 1, 2026, 12:43 a.m. |
| PD | Predicate disambiguation | batch_69cc5edf84408190aa5f57cb8bfd00e1 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:07 p.m.