Triple
T2212167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kona International Airport |
E50941
|
entity |
| Predicate | supportsInternationalCharters |
P33077
|
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: [Kona International Airport, supportsInternationalCharters, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsInternationalCharters Context triple: [Kona International Airport, supportsInternationalCharters, true]
-
A.
supportsSchengenFlights
Indicates that an entity enables or accommodates flights operating within the Schengen Area.
-
B.
isInternational
Indicates that something has a connection to, involves, or extends across more than one country.
-
C.
supportsInternationalization
Indicates that an entity provides functionality or features that enable use across multiple languages, locales, or regional formats.
-
D.
includedCharteredCompanyTerritory
Indicates that a territory was part of, or fell within the jurisdiction of, a chartered company’s controlled area.
-
E.
supportsNonSchengenFlights
chosen
Indicates that the subject facility or service is capable of handling or accommodating flights that operate outside the Schengen Area.
- 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_69a88b06709c8190978fb2418470d1b6 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abbfecea6c8190b762bbfda8490e31 |
completed | March 7, 2026, 6:04 a.m. |
| PD | Predicate disambiguation | batch_69abbdaa26d48190860c33fd464c4845 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.