Triple
T3601836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Employer Support of the Guard and Reserve |
E76273
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | employer outreach program |
C2588
|
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: employer outreach program Context triple: [Employer Support of the Guard and Reserve, instanceOf, employer outreach program]
-
A.
professional outreach initiative
chosen
A professional outreach initiative is a structured effort by an organization or individual to build relationships, share expertise, and create opportunities with targeted external audiences in their field.
-
B.
public employment program
A public employment program is a government-initiated scheme that directly creates temporary or permanent jobs, typically in public works or community services, to reduce unemployment and support income for targeted populations.
-
C.
online recruitment platform
An online recruitment platform is a digital system that connects employers and job seekers by enabling job postings, candidate search, application management, and communication throughout the hiring process.
-
D.
education and outreach program
An education and outreach program is an organized set of activities designed to inform, engage, and empower target audiences through learning opportunities and community-focused communication.
-
E.
recruitment poster
A recruitment poster is a visually striking printed or digital advertisement designed to attract and motivate individuals to join an organization, cause, or activity by highlighting its benefits, values, and opportunities.
- 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_69ad85d93dcc819094fba90cf70f4996 |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:22 p.m.