Triple
T12088288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bangor International Airport |
E287867
|
entity |
| Predicate | isRefuelingStopFor |
P98902
|
FINISHED |
| Object | transatlantic 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: transatlantic flights | Statement: [Bangor International Airport, isRefuelingStopFor, transatlantic flights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRefuelingStopFor Context triple: [Bangor International Airport, isRefuelingStopFor, transatlantic flights]
-
A.
hasRefuellingCapabilityFor
Indicates that one entity is capable of providing or performing refuelling operations for another entity.
-
B.
isStopoverSiteFor
chosen
Indicates that a location serves as a temporary stopping or resting point along the route or journey of another entity.
-
C.
hasPumpingStation
Indicates that one entity possesses, contains, or is served by a pumping station associated with it.
-
D.
hasFuelServices
Indicates that one entity provides or is equipped with fuel-related services or facilities for another entity.
-
E.
hasStopArea
Indicates that an entity is associated with or contains a specific stop area, such as a designated location where vehicles stop.
- 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_69d6ab4964708190850585628b287b0c |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9178ad99c8190a54777b9bbe998bc |
completed | April 10, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69d915000454819089fee00022055599 |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:48 p.m.