Triple
T32196637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Achieving a Better Life Experience Act of 2014 |
E822419
|
entity |
| Predicate | accountName |
P163648
|
FINISHED |
| Object | ABLE account |
—
|
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: ABLE account | Statement: [Achieving a Better Life Experience Act of 2014, accountName, ABLE account]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accountName Context triple: [Achieving a Better Life Experience Act of 2014, accountName, ABLE account]
-
A.
associatedName
Indicates that one entity has an alternative or related name that is linked or connected to another entity.
-
B.
credentialName
Indicates the specific title or label assigned to a credential associated with an entity.
-
C.
accountType
Indicates the specific category or classification of an account within a system or context.
-
D.
depositName
chosen
Indicates that an entity has or is associated with a specific name identifying a deposit.
-
E.
chargeName
Indicates the specific name or label assigned to a charge or accusation associated with an entity.
- 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_69f349093174819086e633c190a51aa8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bb38af6c819082ad0dacc7acf54e |
completed | May 3, 2026, 3:04 a.m. |
| PD | Predicate disambiguation | batch_69f6b3aa892481908d29283a074e6722 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:36 a.m.