Triple
T3747490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Air Force aircraft designation system |
E81242
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aircraft designation system |
C5344
|
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: aircraft designation system Context triple: [Royal Air Force aircraft designation system, instanceOf, aircraft designation system]
-
A.
aircraft designation
chosen
An aircraft designation is a standardized alphanumeric code that identifies an aircraft’s type, role, and variant within a specific classification system.
-
B.
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.
-
C.
aircraft call sign
An aircraft call sign is a unique alphanumeric identifier used in radio communications to distinguish one aircraft or flight from all others.
-
D.
aircraft registration prefix
An aircraft registration prefix is a standardized code, usually based on a country’s international identifier, that appears at the beginning of an aircraft’s registration mark to indicate its state of registration.
-
E.
aircraft registration
An aircraft registration is a unique alphanumeric identifier assigned by a national aviation authority to an individual aircraft for legal, operational, and tracking purposes.
- 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_69ad8b19b7b08190a6188804e99c53e9 |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3:35 p.m.