Triple
T10144959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Marine Corps History Division |
E231680
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military history organization |
C10615
|
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: military history organization Context triple: [United States Marine Corps History Division, instanceOf, military history organization]
-
A.
military history
Military history is the study of armed conflict across time, examining wars, battles, strategies, technologies, and their political, social, and cultural impacts on societies.
-
B.
historical armed forces
Historical armed forces are organized military institutions from past eras, composed of soldiers, equipment, and command structures, created by states or societies to conduct warfare, defend territories, and project power.
-
C.
military organization
A military organization is a structured group of armed forces personnel and resources, organized under a defined hierarchy and command system, to plan, coordinate, and conduct defense and combat operations in support of a state’s strategic objectives.
-
D.
military historian
A military historian is a scholar who researches, analyzes, and interprets past and present armed conflicts, military institutions, strategies, and their broader social and political impacts.
-
E.
history organization
chosen
A history organization is an entity dedicated to researching, preserving, interpreting, and promoting understanding of past events, cultures, and narratives through activities such as archiving, education, and public outreach.
- 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_69ca848364f881908a24366a6feec1db |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 9:07 p.m.