Triple
T13488904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Centennial Airport |
E318580
|
entity |
| Predicate | hasCorporateAviation |
P110600
|
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: [Centennial Airport, hasCorporateAviation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCorporateAviation Context triple: [Centennial Airport, hasCorporateAviation, yes]
-
A.
hasGeneralAviationActivity
Indicates that an entity is involved in or supports non-commercial, private, or recreational aviation operations.
-
B.
hasGeneralAviationFacilities
Indicates that a location or airport provides facilities and services specifically for general aviation operations.
-
C.
servesAviationType
Indicates that one entity provides services or functions specifically for a particular type or category of aviation.
-
D.
hasCorporateFlightDepartments
Indicates that an entity maintains one or more internal departments responsible for managing and operating its corporate aircraft and related flight operations.
-
E.
isPartOfAviationSystem
Indicates that something functions as a component or subsystem within a broader aviation system or infrastructure.
- F. None of above. chosen
Provenance (4 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_69d806b6bfec819089222715b2e86c8e |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf3b9b488190bb4e11424ff599c8 |
completed | April 12, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69dbae06061881909a6a6032e0507587 |
completed | April 12, 2026, 2:36 p.m. |
| PDg | Predicate description generation | batch_69dbaecc98cc8190829f5be759c4f1e3 |
completed | April 12, 2026, 2:40 p.m. |
Created at: April 9, 2026, 9:43 p.m.