Triple
T1021041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greater Sudbury Airport |
E22038
|
entity |
| Predicate | hasBasedOperator |
P22525
|
FINISHED |
| Object | air ambulance operator |
—
|
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: air ambulance operator | Statement: [Greater Sudbury Airport, hasBasedOperator, air ambulance operator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBasedOperator Context triple: [Greater Sudbury Airport, hasBasedOperator, air ambulance operator]
-
A.
hasFixedBaseOperator
Indicates that an entity is associated with or utilizes a specific, non-changing base operator as part of its definition or behavior.
-
B.
hasOperationType
Indicates the specific kind or category of operation associated with an entity or process.
-
C.
usedByOperator
chosen
Indicates that something is utilized or operated by a particular operator or operating entity.
-
D.
hasSupportBase
Indicates that one entity serves as the supporting base or foundation upon which another entity rests, is mounted, or is structurally stabilized.
-
E.
operatesBase
Indicates that an organization or agent runs or manages a primary facility, location, or base of operations.
- 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_69a493d6e380819097b384986ffc315c |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7dd76b081909ed4d2f7adb6480d |
completed | March 1, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69a4b724c7908190a5b92a57fbdbff4e |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.