Triple
T9979041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CASA CN-235 |
E196402
|
entity |
| Predicate | takeoffPerformance |
P62022
|
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: [CASA CN-235, takeoffPerformance, short takeoff and landing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: takeoffPerformance Context triple: [CASA CN-235, takeoffPerformance, short takeoff and landing]
-
A.
takeoffPower
Indicates the power level an aircraft or engine produces specifically during the takeoff phase of flight.
-
B.
takeoffCharacteristic
chosen
Indicates the specific properties or conditions associated with how an entity takes off, such as its manner, performance, or requirements during takeoff.
-
C.
takeoffDistanceCharacteristic
Indicates the relationship between an aircraft (or flight operation) and a characteristic describing the distance required or used for takeoff.
-
D.
takeoffBase
Indicates the location or base from which a takeoff (such as of an aircraft or flight) originates.
-
E.
takeoffMethod
Indicates the method or procedure by which an aircraft or object initiates its takeoff from a surface or launch point.
- 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_69ca82efbce081908179b4b9c65096eb |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb850bde48190a06b77757f8c081b |
completed | April 2, 2026, 12:29 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9daa808190b413a1b9a1e929e2 |
completed | April 1, 2026, 1:29 p.m. |
Created at: March 30, 2026, 8:49 p.m.