Triple
T11712379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Civil Service Retirement System |
E278402
|
entity |
| Predicate | benefitPaymentForm |
P10121
|
FINISHED |
| Object | lifetime annuity |
—
|
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: lifetime annuity | Statement: [Civil Service Retirement System, benefitPaymentForm, lifetime annuity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: benefitPaymentForm Context triple: [Civil Service Retirement System, benefitPaymentForm, lifetime annuity]
-
A.
benefitForm
chosen
Indicates that one entity is a specific form, type, or variant in which a benefit is provided or realized for another entity.
-
B.
taxpayerBenefitForm
Indicates that there is a specific form documenting or enabling a benefit granted to a taxpayer.
-
C.
benefitStructure
Indicates a relationship where one entity defines, organizes, or governs the benefits (such as advantages, compensations, or perks) provided to or associated with another entity.
-
D.
benefitAdministered
Indicates that a benefit (such as aid, service, or entitlement) has been formally provided or delivered to an eligible recipient by an administering party.
-
E.
benefitAvailableAt
Indicates that a particular benefit can be obtained, accessed, or used at a specified location, time, or context.
- 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_69d6aaff2ce88190b4a1e4b341ad5377 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4be10088190854699385d1f6a95 |
completed | April 10, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69d88a7d483081909c2a101087515d74 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.