Triple
T24114229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pilatus PC-24 |
E597461
|
entity |
| Predicate | specialCapability |
P109271
|
FINISHED |
| Object | short takeoff and landing |
—
|
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: short takeoff and landing | Statement: [Pilatus PC-24, specialCapability, short takeoff and landing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specialCapability Context triple: [Pilatus PC-24, specialCapability, short takeoff and landing]
-
A.
featuresSpecialAbility
chosen
Indicates that an entity possesses or is characterized by a particular special ability.
-
B.
capabilityType
Indicates the type or category of capability that an entity possesses or is associated with.
-
C.
primaryCapability
Indicates that one entity serves as the main or most important functional ability, role, or competence of another entity.
-
D.
consideredCapability
Indicates that something is regarded or evaluated as a potential capability of an entity.
-
E.
specialFeature
Indicates that an entity possesses a distinctive or noteworthy attribute, capability, or characteristic that sets it apart from others.
- 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_69e288c74200819098ab875b592cb39f |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1de1daf0481908767902bdf4e3682 |
completed | April 29, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:04 p.m.