Triple
T14171426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BPS-17 |
E351215
|
entity |
| Predicate | seniorityRole |
P92411
|
FINISHED |
| Object | starting cadre for many occupational groups |
—
|
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: starting cadre for many occupational groups | Statement: [BPS-17, seniorityRole, starting cadre for many occupational groups]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seniorityRole Context triple: [BPS-17, seniorityRole, starting cadre for many occupational groups]
-
A.
seniorRank
Indicates that one entity holds a higher or more senior rank or position than another entity.
-
B.
typicalSeniorityLevel
chosen
Indicates the usual or most common rank or seniority level associated with an entity in a given context.
-
C.
hasPermanentSeniority
Indicates that one entity holds a fixed, enduring precedence or higher rank over another that does not change over time.
-
D.
successorInSomeRoles
Indicates that one entity has taken over or followed another entity in certain specified roles or positions.
-
E.
ordinationRole
Indicates the specific religious or ceremonial office, function, or capacity in which an entity is formally ordained.
- 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_69d8278834a08190b0f1784e58d7b99c |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61b5dcbc8190b0cfcce5e6c6d582 |
completed | April 14, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69de05baed64819096590e5618a3a8ed |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:01 a.m.