Triple
T17366845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RASigs |
E422207
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Royal Australian Corps of Signals |
C38485
|
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: Royal Australian Corps of Signals Context triple: [RASigs, instanceOf, Royal Australian Corps of Signals]
-
A.
United States Army signal brigade
A United States Army signal brigade is a specialized military unit responsible for planning, installing, operating, and maintaining tactical and strategic communications and information systems to support command and control across the battlefield.
-
B.
Royal Australian Air Force unit
A Royal Australian Air Force unit is an organizational entity within the RAAF, composed of personnel, aircraft, and equipment structured to perform specific operational, training, or support roles in air and space power.
-
C.
Royal Australian Air Force unit elements
Royal Australian Air Force unit elements are the organizational components—such as squadrons, wings, and support units—that structure, operate, and sustain the RAAF’s air power capabilities.
-
D.
Army Materiel Command
Army Materiel Command is the U.S. Army organization responsible for developing, procuring, distributing, sustaining, and managing equipment, supplies, and materiel to support Army operations worldwide.
-
E.
Royal Australian Air Force wing
A Royal Australian Air Force wing is a major operational or support formation comprising multiple squadrons and units, responsible for coordinating and delivering specific air power capabilities within the RAAF.
- 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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:44 a.m.