Triple
T36760069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Do 228-200 |
E908170
|
entity |
| Predicate | STOLCapability |
P53274
|
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: [Do 228-200, STOLCapability, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: STOLCapability Context triple: [Do 228-200, STOLCapability, yes]
-
A.
shortTakeoffAndLandingCapability
chosen
Indicates that an entity has the ability to take off and land safely on runways or surfaces that are significantly shorter than standard operational requirements.
-
B.
landingDistanceSTOL
Indicates the distance required for an aircraft to land and come to a stop when using short takeoff and landing (STOL) procedures.
-
C.
hasTakeoffAndLandingCapability
Indicates that an entity possesses the ability to both take off and land, typically under its own operational power or design.
-
D.
landingCapability
Indicates the ability or suitability of an entity (e.g., a vehicle or system) to perform a landing under specified conditions.
-
E.
stallSpeed
Indicates the minimum speed at which an aircraft (or similar vehicle) can fly while still maintaining sufficient lift to avoid stalling.
- 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_69f76e779bec8190be0e1f87a131e0f4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c9f5a8848190ba956ff27f44e396 |
completed | May 3, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:12 p.m.