Triple
T2801112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supplemental Security Income |
E53154
|
entity |
| Predicate | programCategory |
P2192
|
FINISHED |
| Object | safety net program |
—
|
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: safety net program | Statement: [Supplemental Security Income, programCategory, safety net program]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programCategory Context triple: [Supplemental Security Income, programCategory, safety net program]
-
A.
programType
chosen
Indicates the category or kind of program to which an entity belongs or with which it is associated.
-
B.
programFocus
Indicates that an educational or training program is primarily oriented around or concentrated on a particular subject, theme, or objective.
-
C.
program
Indicates that an entity creates, writes, or develops a computer program or software application.
-
D.
scriptCategory
Indicates the classification or type of script to which an entity (such as a written work, code, or performance text) belongs.
-
E.
programsConsolidatedInto
Indicates that multiple separate programs have been merged or combined into a single, unified program.
- 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_69ab495a90788190941b6917e1eca3a6 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abde2ec2ac8190bd702ad3eafb6aed |
completed | March 7, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69abdd059f308190853191f6ffe2bc6f |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:58 p.m.