Triple
T32118635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SNCO |
E820304
|
entity |
| Predicate | hasRankPayGradeRange |
P16498
|
FINISHED |
| Object | E-7 to E-9 |
—
|
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 to E-9 | Statement: [SNCO, hasRankPayGradeRange, E-7 to E-9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRankPayGradeRange Context triple: [SNCO, hasRankPayGradeRange, E-7 to E-9]
-
A.
isAbovePayGrade
Indicates that one entity’s authority, responsibility, or required seniority level exceeds the other’s official position or compensation level.
-
B.
hasEmployeeRange
Indicates the range or limits on the number of employees associated with an entity.
-
C.
hasRankOrTitle
Indicates that an entity holds, is assigned, or is associated with a specific rank, title, or formal designation.
-
D.
hasRankCategory
Indicates that an entity is assigned to a particular rank-based classification or level within an ordered hierarchy.
-
E.
rankRange
chosen
Indicates that an entity’s rank falls within a specified minimum and maximum range.
- 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_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 1, 2026, 12:28 a.m.