Triple
T35995161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kauai island airports |
E1040960
|
entity |
| Predicate | mainUses |
P51748
|
FINISHED |
| Object | scheduled passenger flights (Lihue Airport) |
—
|
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: scheduled passenger flights (Lihue Airport) | Statement: [Kauai island airports, mainUses, scheduled passenger flights (Lihue Airport)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainUses Context triple: [Kauai island airports, mainUses, scheduled passenger flights (Lihue Airport)]
-
A.
mainlyUses
chosen
Indicates that one entity primarily relies on, employs, or utilizes another entity as its main tool, method, resource, or medium.
-
B.
primaryUseOf
Indicates that one entity serves as the main or principal function, purpose, or application of another entity.
-
C.
majorUse
Indicates that something serves as the primary or most significant use or application of an entity.
-
D.
primaryCurrentUse
Indicates the main way something is currently being used or its principal present function.
-
E.
primaryUseStart
Indicates the point in time or event at which the primary use or main function of something begins.
- 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_69f76e29084c819083987b828d414de7 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7acaec1508190a38f2ac9cc5383e7 |
completed | May 3, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f7ab75387c819091afc3c2128eb903 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.