Triple
T23719911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Marine Corps personnel |
E586111
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | armed forces members |
C7744
|
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: armed forces members Context triple: [U.S. Marine Corps personnel, instanceOf, armed forces members]
-
A.
military personnel category
A military personnel category is a classification that groups service members based on roles, ranks, duties, or service status within the armed forces.
-
B.
American military personnel
chosen
American military personnel are individuals who serve in the United States Armed Forces, including the Army, Navy, Air Force, Marine Corps, Space Force, and Coast Guard, in roles ranging from combat and support to technical and administrative duties.
-
C.
auxiliary military personnel
Auxiliary military personnel are non-regular service members who provide specialized or supporting functions—such as logistics, medical aid, intelligence, or technical services—to enhance and sustain the operations of a primary armed force.
-
D.
military community
A military community is a social group composed of service members, their families, veterans, and supporting personnel who share common experiences, resources, and culture related to military life.
-
E.
Armenian military personnel
Armenian military personnel are individuals who serve in Armenia’s armed forces, responsible for the defense, security, and military operations of the Republic of Armenia.
- 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_69e24906fb108190a6898751e46bdc11 |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 7 p.m.