Triple
T17420151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Humberside Airport |
E423589
|
entity |
| Predicate | hasHelicopterRole |
P122116
|
FINISHED |
| Object | offshore support |
—
|
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: offshore support | Statement: [Humberside Airport, hasHelicopterRole, offshore support]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHelicopterRole Context triple: [Humberside Airport, hasHelicopterRole, offshore support]
-
A.
isHelicopterOf
Indicates that one entity is a helicopter that belongs to, is operated by, or is otherwise associated with another entity.
-
B.
hasHelicopterTrainingRole
Indicates that an entity holds a role or position specifically related to the training or instruction of helicopter operations.
-
C.
isHelicopterOnly
Indicates that the subject is restricted to or designated exclusively for use by helicopters.
-
D.
canOperateHelicopterType
Indicates that one entity has the ability, qualification, or authorization to operate or pilot a specified type of helicopter.
-
E.
helicopterService
chosen
Indicates that one entity provides or operates a helicopter-based transportation or support service for another entity or location.
- 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_69d889d7d27c819088486ce3f0627fa1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e44236419c8190a106748bca6f30cd |
completed | April 19, 2026, 2:47 a.m. |
| PD | Predicate disambiguation | batch_69e3b02e6cc88190986e85e64ce9383e |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:46 a.m.