Triple
T14416468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charlevoix Municipal Airport |
E357464
|
entity |
| Predicate | supportsRegionalConnectivity |
P99269
|
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: [Charlevoix Municipal Airport, supportsRegionalConnectivity, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsRegionalConnectivity Context triple: [Charlevoix Municipal Airport, supportsRegionalConnectivity, Yes]
-
A.
supportsRegion
Indicates that one entity provides assistance, resources, or backing to a specific geographic or administrative region.
-
B.
supportsRegionRestriction
Indicates that an entity enforces or accommodates limitations on availability or access based on geographic regions.
-
C.
hasRegionalServices
chosen
Indicates that an entity provides or is associated with services that operate within a specific geographic region or set of regions.
-
D.
connectsCountryOrRegion
Indicates that one entity establishes a connection, link, or association to a specific country or region.
-
E.
supportsTerminalConnections
Indicates that one entity is capable of handling or enabling direct connections to terminal interfaces or endpoints.
- 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_69d82793421c8190861eb0e673b085de |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de90cec8e4819087c72d82f9caacda |
completed | April 14, 2026, 7:09 p.m. |
| PD | Predicate disambiguation | batch_69de5c30467881908e770e3940295641 |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:17 a.m.