Triple
T2909806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Navy ranks |
E63653
|
entity |
| Predicate | lowestEnlistedPaygrade |
P7397
|
FINISHED |
| Object | E-1 |
—
|
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 | Statement: [United States Navy ranks, lowestEnlistedPaygrade, E-1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lowestEnlistedPaygrade Context triple: [United States Navy ranks, lowestEnlistedPaygrade, E-1]
-
A.
highestNonCommissionedRank
Indicates that the subject holds the top position among all non-commissioned ranks within a given hierarchy or organization.
-
B.
lowestRank
Indicates that the subject has the least or worst rank in an ordered set compared to all other related entities.
-
C.
lowestGrade
Indicates that one entity has the smallest or worst grade value compared to all other relevant entities in a given context.
-
D.
payGrade
chosen
Indicates the level or category of compensation assigned to an entity, typically reflecting its rank, role, or seniority in a pay structure.
-
E.
ageAtEnlistment
Indicates the age a person was when they enlisted in a service, organization, or role.
- 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_69ab4c44ab448190b9411324e8a1fc1d |
completed | March 6, 2026, 9:51 p.m. |
| NER | Named-entity recognition | batch_69abe0e899808190a348e1e71116d0a5 |
completed | March 7, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69abdd1b77608190b20fc078fdb85e64 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:11 p.m.