Triple
T9763771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Master Gunnery Sergeant |
E236732
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States Marine Corps rank |
C26202
|
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: United States Marine Corps rank Context triple: [Master Gunnery Sergeant, instanceOf, United States Marine Corps rank]
-
A.
United States Marine Corps position
A United States Marine Corps position is a specific role or billet within the Marine Corps organization that defines an individual's duties, responsibilities, and place in the military hierarchy.
-
B.
component of the United States Marine Corps
A component of the United States Marine Corps is a distinct organizational element, such as a command, unit, or supporting establishment, that contributes specific capabilities and functions to the Corps’ overall mission.
-
C.
United States Marine Corps order
A United States Marine Corps order is an official directive issued by authorized Marine Corps leadership that prescribes policies, procedures, or actions to be followed by Marines and Marine Corps units.
-
D.
regiment of the United States Marine Corps
A regiment of the United States Marine Corps is a mid-level, combat-capable organizational unit typically composed of several battalions, providing command, control, and support for large-scale Marine operations.
-
E.
army rank
An army rank is a formal level of authority and responsibility within a military hierarchy that defines a soldier’s position, duties, and chain-of-command relationships.
- 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_69ca84d64f6c8190a4ed4e9f5936eda5 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:25 p.m.