Triple
T33633100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MCPO |
E861618
|
entity |
| Predicate | minimumPayGrade |
P7397
|
FINISHED |
| Object | 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-9 | Statement: [MCPO, minimumPayGrade, E-9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minimumPayGrade Context triple: [MCPO, minimumPayGrade, E-9]
-
A.
minimumGrant
Indicates that there is a lowest allowable or required amount of a grant associated with an entity or agreement.
-
B.
payGrade
chosen
Indicates the level or category of compensation assigned to an entity, typically reflecting its rank, role, or seniority in a pay structure.
-
C.
minimumLevel
Indicates that one entity specifies the lowest allowable or required level, degree, or threshold at which another entity, condition, or action becomes valid or applicable.
-
D.
minimumContribution
Indicates the smallest allowable or required amount that an entity must contribute in a given context or relationship.
-
E.
minimumDenomination
Indicates that one entity specifies the smallest allowable unit or value (minimum denomination) in which another entity can be expressed, transacted, or divided.
- 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_69f34981c54c81909b33c3fa2208a52d |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70fb4f18c819099ef6d9177b7d205 |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:41 a.m.