Triple
T4549249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kate |
E110121
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Allied reporting name |
C14199
|
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 reporting name Context triple: [Kate, instanceOf, Allied reporting name]
-
A.
NATO reporting name
chosen
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.
-
B.
aircraft reporting name
An aircraft reporting name is a standardized, often code-like designation assigned to an aircraft type—typically by foreign militaries or intelligence organizations—to simplify identification, communication, and reference.
-
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.
wartime codename
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.
-
E.
Allied occupation body
An Allied occupation body is an administrative authority established by victorious Allied powers to govern, oversee reconstruction, and implement political, economic, and legal reforms in a defeated or occupied territory following conflict.
- 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_69bd4412524c8190be5bcc9ddee91848 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:05 p.m.