Triple
T13626806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lee's Summit Municipal Airport |
E325604
|
entity |
| Predicate | hasIfrCapability |
P100613
|
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: [Lee's Summit Municipal Airport, hasIfrCapability, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIfrCapability Context triple: [Lee's Summit Municipal Airport, hasIfrCapability, yes]
-
A.
hasFeature
Indicates that an entity possesses, exhibits, or includes a particular characteristic, attribute, or component.
-
B.
hasSupported
Indicates that one entity has provided assistance, endorsement, or backing to another entity, either materially, emotionally, or through advocacy.
-
C.
hasFeatureStatus
chosen
Indicates that an entity possesses a particular feature along with its current state or condition.
-
D.
usesFinFlash
Indicates that one entity employs or displays a fin-based flashing signal or pattern in relation to another entity.
-
E.
hasPortCapability
Indicates that an entity possesses the ability or feature to support, provide, or utilize a specific type of port or port-related function.
- 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_69d8076aae28819092cf636190ee5529 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc60635d08190899806fe8936f02a |
completed | April 12, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69dbbe85e1c4819095194f4b7f9f6118 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:51 p.m.