Triple
T24981055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Department of the Army civilians |
E625167
|
entity |
| Predicate | recruitmentPlatform |
P157499
|
FINISHED |
| Object | USAJOBS |
—
|
NE NERFINISHED |
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: USAJOBS | Statement: [Department of the Army civilians, recruitmentPlatform, USAJOBS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recruitmentPlatform Context triple: [Department of the Army civilians, recruitmentPlatform, USAJOBS]
-
A.
recruitmentFrom
Indicates that one entity recruits or sources members, employees, or participants from another entity.
-
B.
recruitingFocus
Indicates that an entity’s recruitment efforts are specifically directed toward or concentrated on another entity or group.
-
C.
recruitmentBase
Indicates the foundational source, location, or context from which recruitment efforts or recruited entities originate.
-
D.
careerWalks
Indicates the total number of bases on balls (walks) a player has received over the course of their entire career.
-
E.
recruitingRanking
Indicates the relative standing or quality level assigned to an entity based on its effectiveness or success in recruiting participants, members, or talent.
- F. None of above. chosen
Provenance (4 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_69e2ff254570819093d197b1900305ac |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f4490636f88190b8e614202f6d7a65 |
completed | May 1, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
| PDg | Predicate description generation | batch_69f448fe11f08190bdd53ca7ba2d51e4 |
completed | May 1, 2026, 6:32 a.m. |
Created at: April 18, 2026, 6:02 a.m.