Triple
T14385566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marine Corps boot camp |
E356713
|
entity |
| Predicate | targetRecruits |
P100977
|
FINISHED |
| Object | civilian enlistees |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: civilian enlistees | Statement: [Marine Corps boot camp, targetRecruits, civilian enlistees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetRecruits Context triple: [Marine Corps boot camp, targetRecruits, civilian enlistees]
-
A.
recruitsFor
Indicates that one entity actively seeks out, enlists, or brings in participants, members, or resources on behalf of another entity, such as an organization, event, or cause.
-
B.
recruitingFocus
chosen
Indicates that an entity’s recruitment efforts are specifically directed toward or concentrated on another entity or group.
-
C.
recruitmentFrom
Indicates that one entity recruits or sources members, employees, or participants from another entity.
-
D.
targetOfficeSought
Indicates the specific public or organizational office or position that an individual is seeking or running for.
-
E.
targetCandidate
Indicates that an entity is being considered or designated as a potential target for selection, action, or further evaluation.
- F. None of above.
Provenance (3 batches)
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_69d827927c988190ad98bb0360981783 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de9025cff881908c08224d90d9f750 |
completed | April 14, 2026, 7:06 p.m. |
| PD | Predicate disambiguation | batch_69de2aa024c48190805df6a9d63deb10 |
completed | April 14, 2026, 11:53 a.m. |
Created at: April 10, 2026, 1:16 a.m.