Triple
T25723244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USPHS O-7 |
E645045
|
entity |
| Predicate | payPlan |
P8653
|
FINISHED |
| Object | Uniformed Services pay system |
—
|
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: Uniformed Services pay system | Statement: [USPHS O-7, payPlan, Uniformed Services pay system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: payPlan Context triple: [USPHS O-7, payPlan, Uniformed Services pay system]
-
A.
paymentStructure
Indicates how payments are organized, scheduled, and divided between the involved parties.
-
B.
payType
Indicates the method or category of payment used in a transaction or compensation arrangement.
-
C.
billingMethod
Indicates the way in which payment is arranged, processed, or charged for a product, service, or account.
-
D.
repaymentPlanOptions
Indicates the available ways or schedules by which a debt or obligation can be repaid.
-
E.
planType
chosen
Indicates the specific category or kind of plan associated with an entity, such as its level, structure, or intended use.
- 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_69e77e8476fc8190bd5e9d05b89fad0a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fc683cd48190bf4bab9cb8de691a |
completed | May 2, 2026, 1:30 p.m. |
| PD | Predicate disambiguation | batch_69f480824a1c81908a8a492eedbc2596 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 10:05 p.m.