Triple
T26990211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marine Corps publications |
E679844
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States Marine Corps document |
C8923
|
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 document Context triple: [Marine Corps publications, instanceOf, United States Marine Corps document]
-
A.
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.
-
B.
U.S. Department of Defense strategic document
A U.S. Department of Defense strategic document is an official, high-level publication that outlines long-term defense objectives, priorities, and plans for employing military resources to protect national security interests.
-
C.
United States military manual
chosen
A United States military manual is an official publication that provides standardized doctrine, procedures, and guidance for the organization, training, and operations of U.S. armed forces.
-
D.
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.
-
E.
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.
- 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_69eeeb5138ac8190b3c273ddc659a54f |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 27, 2026, 6:51 a.m.