Triple
T13924154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BPS-4 |
E334818
|
entity |
| Predicate | payScaleLevel |
P7397
|
FINISHED |
| Object | lower-middle grade |
—
|
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: lower-middle grade | Statement: [BPS-4, payScaleLevel, lower-middle grade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: payScaleLevel Context triple: [BPS-4, payScaleLevel, lower-middle grade]
-
A.
payGrade
chosen
Indicates the level or category of compensation assigned to an entity, typically reflecting its rank, role, or seniority in a pay structure.
-
B.
payScale
Indicates the compensation level or salary range assigned to an entity, typically reflecting its relative pay or grade within a structured system.
-
C.
payGradeComparison
Indicates that the relative pay grade or salary level between two entities is being compared (e.g., one is higher, lower, or equal to the other).
-
D.
salaryMilestone
Indicates a specific salary-related threshold or achievement that has been reached or is being targeted in relation to an entity.
-
E.
salary
Indicates the amount of monetary compensation an entity receives, typically on a regular basis, for work or services performed.
- 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_69d81c5f739081908bc05b2461f54828 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2aa6cd9881908f652538f4613f37 |
completed | April 14, 2026, 11:53 a.m. |
| PD | Predicate disambiguation | batch_69de059e4ba881908554f72e889719fa |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:16 p.m.