Triple
T14999158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AF 8x-xxxx |
E374037
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States military aircraft serial number format element |
C35386
|
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: United States military aircraft serial number format element Context triple: [AF 8x-xxxx, instanceOf, United States military aircraft serial number format element]
-
A.
aircraft designation prefix
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).
-
B.
aircraft designation
An aircraft designation is a standardized alphanumeric code that identifies an aircraft’s type, role, and variant within a specific classification system.
-
C.
national aircraft marking
A national aircraft marking is a standardized emblem or set of symbols applied to an aircraft to indicate its country of registration or military nationality.
-
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.
aircraft tail marking
An aircraft tail marking is a visual identifier, such as symbols, colors, or codes, applied to the tail section of an aircraft to denote its operator, nationality, unit, or other organizational affiliation.
- F. None of above. chosen
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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 2:54 a.m.