Triple
T25930076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Title XXI of the Social Security Act |
E653414
|
entity |
| Predicate | programAcronym |
P39300
|
FINISHED |
| Object | CHIP |
—
|
NE NERFINISHED |
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: CHIP | Statement: [Title XXI of the Social Security Act, programAcronym, CHIP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programAcronym Context triple: [Title XXI of the Social Security Act, programAcronym, CHIP]
-
A.
acronymOfCreatedProgram
chosen
Indicates that one entity is the acronym or abbreviated name of a program that was created or developed as represented by the other entity.
-
B.
programType
Indicates the category or kind of program to which an entity belongs or with which it is associated.
-
C.
developerAcronym
Indicates that an acronym is used as a shortened or abbreviated form of a developer-related term, title, or concept.
-
D.
programDesignation
Indicates that an entity is assigned or identified by a specific program designation or label.
-
E.
program
Indicates that an entity creates, writes, or develops a computer program or software application.
- 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_69e7ab3eb9b881909c1390690551f868 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f60418322081908411c24d1dc820de |
completed | May 2, 2026, 2:03 p.m. |
| PD | Predicate disambiguation | batch_69f602d07590819085ac34b189613104 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 22, 2026, 8:36 a.m.