Triple
T16963573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FBI professional staff |
E411487
|
entity |
| Predicate | hasHiringPath |
P14530
|
FINISHED |
| Object | federal competitive service |
—
|
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: federal competitive service | Statement: [FBI professional staff, hasHiringPath, federal competitive service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHiringPath Context triple: [FBI professional staff, hasHiringPath, federal competitive service]
-
A.
acceptsCareerPath
Indicates that one entity approves or agrees to follow a proposed career path associated with another entity.
-
B.
canHire
Indicates that one entity has the authority or ability to employ or recruit another entity.
-
C.
hasCareerTrack
chosen
Indicates that an entity is associated with or follows a particular career path or professional progression.
-
D.
hasDevelopmentOpportunity
Indicates that an entity offers or possesses a potential for growth, improvement, or advancement, typically in skills, performance, or capabilities.
-
E.
hasRecruitType
Indicates that an entity is associated with a specific type or category of recruitment.
- 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d0a1f6308190af5ad171630dacbf |
completed | April 18, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69e32b9cddf88190bc42709604047353 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:31 a.m.