Triple
T34785552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marine Corps civilian employees |
E1002795
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | civilian personnel category |
C49638
|
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: civilian personnel category Context triple: [Marine Corps civilian employees, instanceOf, civilian personnel category]
-
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.
dual-status civilian employee category
A dual-status civilian employee category refers to individuals who simultaneously hold a civilian position and a compatible military or uniformed service role, subject to the requirements and obligations of both employment statuses.
-
C.
military personnel sub‑component
A military personnel sub-component is a distinct organizational unit or functional group within the armed forces composed of service members assigned specific roles, responsibilities, or capabilities that contribute to the overall mission.
-
D.
civilian official
A civilian official is a non-military government employee who holds administrative or managerial authority in public institutions, implementing policies and overseeing civil affairs.
-
E.
civilian workforce
chosen
The civilian workforce comprises all non-military individuals engaged in paid employment or actively seeking work within an economy, contributing labor and expertise across public and private sectors.
- 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_69f76db47d408190a24fc7164439ea2d |
completed | May 3, 2026, 3:45 p.m. |
Created at: May 3, 2026, 3:59 p.m.