Triple
T30904730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 42nd Cavalry Reconnaissance Squadron |
E787265
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cavalry reconnaissance squadron |
C38179
|
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: cavalry reconnaissance squadron Context triple: [42nd Cavalry Reconnaissance Squadron, instanceOf, cavalry reconnaissance squadron]
-
A.
U.S. Army cavalry squadron
chosen
A U.S. Army cavalry squadron is a battalion-sized, highly mobile combat unit organized to conduct reconnaissance, security, and offensive operations in support of larger maneuver formations.
-
B.
reconnaissance regiment
A reconnaissance regiment is a military unit specialized in gathering intelligence on enemy forces and terrain, typically using mobility, stealth, and advanced surveillance equipment to support larger formations.
-
C.
cavalry battalion
A cavalry battalion is a military unit composed of several cavalry companies or squadrons, organized to conduct mobile reconnaissance, security, and offensive operations, traditionally on horseback and now typically using armored or mechanized vehicles.
-
D.
airborne cavalry unit
An airborne cavalry unit is a highly mobile military force that uses aircraft, typically helicopters, to rapidly deploy troops and conduct reconnaissance, assault, and security operations.
-
E.
cavalry branch
The cavalry branch is a military unit or organizational division specializing in fast, mobile combat forces traditionally mounted on horseback and now often using armored or mechanized vehicles for reconnaissance, flanking, and rapid assault 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_69f224bcbcb48190836df847424e4057 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:50 p.m.