Triple
T19096749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 201st Fighter Squadron |
E467425
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mexican Air Force unit |
C41001
|
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: Mexican Air Force unit Context triple: [201st Fighter Squadron, instanceOf, Mexican Air Force unit]
-
A.
Israeli Air Force unit
An Israeli Air Force unit is an organized military formation within Israel's air arm, responsible for executing specific operational, support, or training missions using assigned aircraft, personnel, and resources.
-
B.
Polish Air Force unit
A Polish Air Force unit is an organizational entity within Poland’s air arm responsible for operating, maintaining, and supporting assigned aircraft and air defense systems to fulfill national defense and allied mission objectives.
-
C.
aviation regiment
An aviation regiment is a military unit composed of multiple aircraft squadrons or flights, along with their supporting personnel and equipment, organized to conduct coordinated air operations.
-
D.
Italian Air Force unit
An Italian Air Force unit is an organizational entity of Italy’s air arm, composed of personnel, aircraft, and support resources structured to perform specific operational, training, or support missions within the national and allied defense framework.
-
E.
Japan Air Self-Defense Force unit
A Japan Air Self-Defense Force unit is an organizational entity within Japan’s air defense branch, composed of personnel, aircraft, and equipment structured to perform specific operational, training, or support missions.
- 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_69d8dd05ac4c8190b1967d8f97f3fb2f |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 12:04 p.m.