Triple
T29994525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CYOO |
E761982
|
entity |
| Predicate | supportsCorporateAviation |
P207200
|
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: [CYOO, supportsCorporateAviation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsCorporateAviation Context triple: [CYOO, supportsCorporateAviation, true]
-
A.
hasCorporateAviation
Indicates that an entity operates, owns, or utilizes aircraft or aviation services for corporate or business purposes.
-
B.
supportsCommercialFlights
Indicates that the subject provides the necessary facilities, services, or conditions for regular commercial passenger or cargo flights to operate.
-
C.
servesAviationType
Indicates that one entity provides services or functions specifically for a particular type or category of aviation.
-
D.
supportsAircraft
Indicates that one entity is capable of accommodating, carrying, or enabling the operation of an aircraft.
-
E.
supportsSingleEngineAircraft
Indicates that the subject is designed, equipped, or authorized to accommodate or be compatible with single-engine aircraft.
- 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_69f224695498819094a81037cad401e2 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 6:39 p.m.