Triple
T27916840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colonel, United States Marine Corps Reserve |
E706096
|
entity |
| Predicate | USPayGrade |
P7397
|
FINISHED |
| Object | O-6 |
—
|
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: O-6 | Statement: [Colonel, United States Marine Corps Reserve, USPayGrade, O-6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: USPayGrade Context triple: [Colonel, United States Marine Corps Reserve, USPayGrade, O-6]
-
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.
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).
-
C.
payScaleNumber
Indicates the specific numeric level or grade assigned to an entity within a pay scale or salary structure.
-
D.
payScale
Indicates the compensation level or salary range assigned to an entity, typically reflecting its relative pay or grade within a structured system.
-
E.
sharesPayGradesWith
Indicates that two entities have equivalent or overlapping pay grade levels within a compensation structure.
- 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_69ef96b6cc808190aab19fb18b235f4b |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63b317e048190963989b732b25b91 |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 6:54 p.m.