Triple
T7847465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 403(b) plan |
E181957
|
entity |
| Predicate | earlyWithdrawalPenaltyAge |
P13299
|
FINISHED |
| Object | 59½ |
—
|
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: 59½ | Statement: [403(b) plan, earlyWithdrawalPenaltyAge, 59½]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earlyWithdrawalPenaltyAge Context triple: [403(b) plan, earlyWithdrawalPenaltyAge, 59½]
-
A.
mandatoryRetirementAge
Indicates the age at which an individual is required by rule or policy to retire from a position or role.
-
B.
minimumAgingTotal
Indicates that the relationship captures the smallest possible total amount of aging (or elapsed time) accumulated across the relevant entities or process.
-
C.
containsAge
Indicates that one entity includes or specifies the age value or age-related information of another entity.
-
D.
ageLimitAppliesAt
chosen
Indicates the specific age or point in time at which an age-related restriction or limit becomes effective for an entity.
-
E.
ageLimitIntroduced
Indicates that a specific age restriction or minimum/maximum age requirement has been formally established or put into effect for something.
- 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_69ca8285d6488190a95d4c02d7354b53 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb164105fc8190a60aaa27dd619d5a |
completed | March 31, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69cae92180f88190ae3d44c3de7adc93 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:49 p.m.