Triple
T3872566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Val |
E92420
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Allied code name |
C3528
|
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: Allied code name Context triple: [Val, instanceOf, Allied code name]
-
A.
wartime codename
chosen
A wartime codename is a deliberately chosen, often cryptic label used to conceal the true nature, identity, or objectives of military operations, units, technologies, or locations during conflict.
-
B.
NATO reporting name
A NATO reporting name is a standardized code word or phrase assigned by NATO to identify and refer to military equipment, particularly aircraft and missiles from non-NATO countries, for clear and consistent communication.
-
C.
Allied military authority
An Allied military authority is a governing body established by cooperating allied nations' armed forces to administer, control, and coordinate military and sometimes civil affairs in occupied or liberated territories during and immediately after conflict.
-
D.
World War II commando raid
A World War II commando raid is a small-scale, highly planned military operation conducted by specially trained troops to infiltrate enemy territory, achieve a specific tactical or strategic objective, and withdraw quickly, often relying on surprise and stealth.
-
E.
Apple project codename
An Apple project codename is a temporary, often thematic internal name used by Apple to identify and reference a product or initiative during its confidential development phase before the official public name is announced.
- 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_69aed967448c819086c4b358d37b25aa |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:20 p.m.