Triple
T19338344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Navy enlisted community |
E483680
|
entity |
| Predicate | hasPayGrades |
P7397
|
FINISHED |
| Object | E-1 through 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-1 through E-9 | Statement: [United States Navy enlisted community, hasPayGrades, E-1 through E-9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPayGrades Context triple: [United States Navy enlisted community, hasPayGrades, E-1 through E-9]
-
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.
sharesPayGradesWith
Indicates that two entities have equivalent or overlapping pay grade levels within a compensation structure.
-
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.
hasGrades
Indicates that an entity possesses or is associated with one or more grade values, typically reflecting evaluations or scores.
-
E.
hasGradeSystem
Indicates that one entity uses, follows, or is governed by a particular grading or evaluation system defined by another 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_69d8e8d244f8819080eb1f3491300db2 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e6185538d48190ae4fa3ac0b0ca182 |
completed | April 20, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69e4dd12303c8190a2027c062b2dff40 |
completed | April 19, 2026, 1:48 p.m. |
Created at: April 10, 2026, 1:33 p.m.