Triple
T18790853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Individual Mobilization Augmentee |
E459508
|
entity |
| Predicate | manpowerCategory |
P11881
|
FINISHED |
| Object | individual augmentee |
—
|
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: individual augmentee | Statement: [Individual Mobilization Augmentee, manpowerCategory, individual augmentee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: manpowerCategory Context triple: [Individual Mobilization Augmentee, manpowerCategory, individual augmentee]
-
A.
employmentBasedCategory
Indicates that one entity’s classification or status is determined by its relationship to employment, such as being based on a specific job, role, or work-related category.
-
B.
hasWorkforceType
Indicates the type or category of workforce associated with an entity (such as permanent, temporary, contract, or part-time).
-
C.
occupationType
Indicates the specific kind or category of work, profession, or role that an entity performs or holds.
-
D.
jobCadre
Indicates that an entity belongs to, or is classified within, a particular job cadre or employment category.
-
E.
personnelType
chosen
Indicates the classification or role category assigned to a person within an organization or system.
- 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5978599008190aaceaff1b1e0a2c7 |
completed | April 20, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69e48d16dd34819096e096d0c0e4c15c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:53 a.m.