Triple
T13889512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BPS-3 |
E333932
|
entity |
| Predicate | typicalJobCategory |
P75042
|
FINISHED |
| Object | support staff positions |
—
|
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: support staff positions | Statement: [BPS-3, typicalJobCategory, support staff positions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalJobCategory Context triple: [BPS-3, typicalJobCategory, support staff positions]
-
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.
occupationType
chosen
Indicates the specific kind or category of work, profession, or role that an entity performs or holds.
-
C.
typicalOccupationsInclude
Indicates that the usual or commonly associated jobs or professions for an entity include the specified occupation(s).
-
D.
careerType
Indicates the kind or category of professional occupation or career path associated with an entity.
-
E.
typeOfWork
Indicates the kind or category of work associated with or performed by an entity.
- 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_69d81c5dd2d48190b7a5fc1e009de936 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de23a3a24881908d81d634622fbbcc |
completed | April 14, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69dd464b1ab48190ae50bfc902bf6ef7 |
completed | April 13, 2026, 7:38 p.m. |
Created at: April 9, 2026, 10:15 p.m.