Triple
T30378025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 69th Infantry Regiment (New York) |
E772746
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | New York Army National Guard unit |
C56834
|
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: New York Army National Guard unit Context triple: [69th Infantry Regiment (New York), instanceOf, New York Army National Guard unit]
-
A.
Oklahoma Army National Guard unit
An Oklahoma Army National Guard unit is a state-based military organization composed of citizen-soldiers who train part-time to provide combat, support, and emergency response capabilities for both state and federal missions.
-
B.
U.S. Army National Guard division
A U.S. Army National Guard division is a large, state-based military formation that can be federally mobilized, combining multiple brigades and support units to conduct sustained combat and support operations alongside active-duty Army forces.
-
C.
National Guard brigade
A National Guard brigade is a large, modular military unit composed of several battalions that can be mobilized by state or federal authorities to conduct combat, support, or emergency response operations.
-
D.
Texas Army National Guard unit
A Texas Army National Guard unit is a state-based military organization composed of part-time citizen-soldiers who train regularly and can be mobilized for both state emergencies and federal missions.
-
E.
Air National Guard operations group
An Air National Guard operations group is a unit-level organization responsible for planning, directing, and executing the flying and operational support missions of an Air National Guard wing.
- 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_69f2248e3444819081b05712dc6873de |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8 p.m.