Triple
T2320418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beechcraft 1900 |
E51165
|
entity |
| Predicate | takeoffConfiguration |
P3541
|
FINISHED |
| Object | short‑haul operations |
—
|
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‑haul operations | Statement: [Beechcraft 1900, takeoffConfiguration, short‑haul operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: takeoffConfiguration Context triple: [Beechcraft 1900, takeoffConfiguration, short‑haul operations]
-
A.
takeoffMethod
Indicates the method or procedure by which an aircraft or object initiates its takeoff from a surface or launch point.
-
B.
takeoffBase
Indicates the location or base from which a takeoff (such as of an aircraft or flight) originates.
-
C.
aircraftConfiguration
chosen
Indicates the specific arrangement or setup of an aircraft’s components, systems, or features for a given purpose or operating condition.
-
D.
takeoffDistanceCharacteristic
Indicates the relationship between an aircraft (or flight operation) and a characteristic describing the distance required or used for takeoff.
-
E.
wingConfiguration
Indicates how the wings of an aircraft or creature are arranged or structured relative to its body and to each other.
- 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_69a88b074b908190ae983dbca7757d88 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc685f05481909c863b29d1f6bacd |
completed | March 7, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69abc5909cc48190aab257313542dc49 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:49 p.m.