Triple
T7847486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 403(b) plan |
E181957
|
entity |
| Predicate | hardshipFeature |
P79346
|
FINISHED |
| Object | may allow hardship withdrawals |
—
|
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: may allow hardship withdrawals | Statement: [403(b) plan, hardshipFeature, may allow hardship withdrawals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hardshipFeature Context triple: [403(b) plan, hardshipFeature, may allow hardship withdrawals]
-
A.
hardship
Indicates that an entity is experiencing or causing significant difficulty, suffering, or adverse conditions.
-
B.
welfareSupportFeature
Indicates that an entity provides, enables, or is associated with some form of welfare-related assistance or support.
-
C.
eligibleFamilies
Indicates that certain families meet the required criteria or conditions to qualify for a specified benefit, service, or program.
-
D.
hasEconomicChallenge
Indicates that an entity is experiencing or facing a financial or economic difficulty, constraint, or problem.
-
E.
hasReliefFeature
Indicates that one entity possesses or includes a specific relief-related physical feature or characteristic.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69caf786ec748190b6347b0c94335550 |
completed | March 30, 2026, 10:21 p.m. |
Created at: March 30, 2026, 4:49 p.m.