Triple
T6669576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orlik |
E151691
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Polish Air Force aircraft designation |
C15091
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Polish Air Force aircraft designation Context triple: [Orlik, instanceOf, Polish Air Force aircraft designation]
-
A.
aircraft designation
An aircraft designation is a standardized alphanumeric code that identifies an aircraft’s type, role, and variant within a specific classification system.
-
B.
aircraft designation prefix
chosen
An aircraft designation prefix is a standardized code or letter sequence placed before an aircraft’s model number to indicate its primary role, function, or configuration (e.g., fighter, transport, trainer).
-
C.
military aircraft nickname
A military aircraft nickname is an informal or semi-official moniker given to a specific aircraft model or type, often reflecting its appearance, role, performance, or reputation among service members and the public.
-
D.
United States presidential aircraft designation
A United States presidential aircraft designation is the specific call sign or model identifier assigned to an aircraft when it is used to transport the President of the United States, such as "Air Force One" for Air Force-operated planes.
-
E.
component of the Soviet Air Forces
A component of the Soviet Air Forces is an organizational unit, formation, or specialized element (such as a regiment, division, or support service) that collectively contributed to the operational, logistical, and strategic capabilities of the USSR’s military aviation.
- F. None of above.
Provenance (1 batch)
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_69c687f71fc081909dbd45d6377f6045 |
completed | March 27, 2026, 1:36 p.m. |
Created at: March 27, 2026, 2:02 p.m.