Triple
T7883428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rudder's Rangers |
E183038
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Texas A&M Corps of Cadets special unit |
C8307
|
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: Texas A&M Corps of Cadets special unit Context triple: [Rudder's Rangers, instanceOf, Texas A&M Corps of Cadets special unit]
-
A.
Texas A&M University unit
A Texas A&M University unit is an organizational entity within the university—such as a college, department, division, or administrative office—responsible for specific academic, research, service, or operational functions.
-
B.
U.S. Army school
A U.S. Army school is a military educational institution that provides specialized training and professional development to soldiers and Army personnel to prepare them for specific roles, missions, and leadership responsibilities.
-
C.
student military organization
chosen
A student military organization is a structured group within an educational institution that provides military-related training, leadership development, and discipline-oriented activities to its student members.
-
D.
U.S. Army center of excellence
A U.S. Army center of excellence is an institutional organization that develops, integrates, and advances specialized doctrine, training, capabilities, and expertise for a specific warfighting or functional area across the Army.
-
E.
Texas A&M University tradition
A Texas A&M University tradition is a long-standing, community-embraced practice or ritual that reflects and reinforces the university’s core values, history, and shared Aggie identity.
- 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_69ca828af6e48190a06ee7010d8f0e64 |
completed | March 30, 2026, 2:02 p.m. |
Created at: March 30, 2026, 4:58 p.m.