Triple
T2196884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cessna 208 Caravan |
E50394
|
entity |
| Predicate | takeoffDistanceCharacteristic |
P36717
|
FINISHED |
| Object | short-field capable |
—
|
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-field capable | Statement: [Cessna 208 Caravan, takeoffDistanceCharacteristic, short-field capable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: takeoffDistanceCharacteristic Context triple: [Cessna 208 Caravan, takeoffDistanceCharacteristic, short-field capable]
-
A.
takeoffDistanceAtMaxWeight
Indicates the distance required for an aircraft to take off when operating at its maximum allowable weight.
-
B.
takeoffMethod
Indicates the method or procedure by which an aircraft or object initiates its takeoff from a surface or launch point.
-
C.
landingDistance
Indicates the required or actual distance needed for an aircraft or object to complete a landing from approach to full stop.
-
D.
takeoffAirportRunway
Indicates the specific airport runway from which an aircraft departs or takes off.
-
E.
runwayLength
Indicates the length of a runway associated with an airport or airfield.
- 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_69a88b044ab48190add007487680f009 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abbf79f3e08190b56e9d7c0ff27237 |
completed | March 7, 2026, 6:02 a.m. |
| PD | Predicate disambiguation | batch_69abbda52328819089c7ab111bebb0ca |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbea8bd4881908f72019a5acf6174 |
completed | March 7, 2026, 5:59 a.m. |
Created at: March 4, 2026, 7:46 p.m.