Triple
T19415098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japan Air Self-Defense Force Airborne Early Warning Group elements |
E485692
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | airborne early warning unit |
C34614
|
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: airborne early warning unit Context triple: [Japan Air Self-Defense Force Airborne Early Warning Group elements, instanceOf, airborne early warning unit]
-
A.
airborne law enforcement unit
An airborne law enforcement unit is a specialized police or security team that uses aircraft to conduct surveillance, support ground operations, pursue suspects, and perform search and rescue or public safety missions from the air.
-
B.
airborne signals unit
chosen
An airborne signals unit is a specialized military or intelligence team equipped on aircraft to detect, intercept, analyze, and relay electronic and communications signals from the air.
-
C.
aviation support unit
An aviation support unit is an organizational entity that provides maintenance, logistics, ground handling, and operational assistance to ensure the effective and safe functioning of aircraft and flight operations.
-
D.
air support unit
An air support unit is a military or emergency response organization equipped with aircraft and personnel to provide reconnaissance, transport, and offensive or defensive support to ground or maritime operations.
-
E.
combat aviation unit
A combat aviation unit is an organized group of military aircraft, aircrew, and support personnel structured to plan, execute, and sustain offensive and defensive air operations.
- 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_69d8e8d688f881909c85104a62e09d8a |
completed | April 10, 2026, 12:11 p.m. |
Created at: April 10, 2026, 1:37 p.m.