Triple
T32118636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SNCO |
E820304
|
entity |
| Predicate | includesPayGrade |
P111934
|
FINISHED |
| Object | E-7 |
—
|
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: E-7 | Statement: [SNCO, includesPayGrade, E-7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesPayGrade Context triple: [SNCO, includesPayGrade, E-7]
-
A.
payGrade
Indicates the level or category of compensation assigned to an entity, typically reflecting its rank, role, or seniority in a pay structure.
-
B.
isAbovePayGrade
Indicates that one entity’s authority, responsibility, or required seniority level exceeds the other’s official position or compensation level.
-
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.
includesGrades
chosen
Indicates that one entity contains or encompasses the grade information associated with another entity.
-
E.
isPaidPosition
Indicates that a role or position involves monetary compensation for the person holding it.
- 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_69f3490209c881908ec0241476715f15 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a01b241f7308190bedb7522cb5dc069 |
completed | May 11, 2026, 10:41 a.m. |
| PD | Predicate disambiguation | batch_6a01b19ff12c81908ee1b188b4a3e118 |
completed | May 11, 2026, 10:38 a.m. |
Created at: May 1, 2026, 12:28 a.m.