Triple
T17548211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doncaster Sheffield Airport |
E427384
|
entity |
| Predicate | hadCargoOperations |
P87144
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Doncaster Sheffield Airport, hadCargoOperations, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadCargoOperations Context triple: [Doncaster Sheffield Airport, hadCargoOperations, true]
-
A.
cargoOperations
chosen
Indicates the handling, movement, and management of cargo during loading, unloading, transfer, or storage activities.
-
B.
hasCargoHandlingMode
Indicates the method or procedure by which cargo is handled, loaded, or unloaded in a given context.
-
C.
hasCargoServices
Indicates that an entity provides or is equipped to handle cargo transportation or freight services for another entity or location.
-
D.
hasCargoDivision
Indicates that an organization possesses a specific division or unit responsible for cargo-related operations or services.
-
E.
hasCargoRole
Indicates that an entity participates in a cargo-related capacity or function within a transport, shipment, or logistics 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_69d889df6dc081908f67dbadc03c07ee |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e454631e148190a1d46a6ecb79c71a |
completed | April 19, 2026, 4:04 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fb39948190a82a597c5bac5c57 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:49 a.m.