Triple
T471058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 81st United States Congress |
E8556
|
entity |
| Predicate | consideredProgram |
P1120
|
FINISHED |
| Object | Fair Deal domestic agenda |
—
|
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: Fair Deal domestic agenda | Statement: [81st United States Congress, consideredProgram, Fair Deal domestic agenda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consideredProgram Context triple: [81st United States Congress, consideredProgram, Fair Deal domestic agenda]
-
A.
implementedProgram
Indicates that an entity has created, developed, or put into operation a particular program or software system.
-
B.
program
Indicates that an entity creates, writes, or develops a computer program or software application.
-
C.
considered
chosen
Indicates that one entity regards, judges, or thinks about another entity in a particular way or context.
-
D.
establishedProgram
Indicates that an entity has created and put into operation a formal program that is now in an active, ongoing state.
-
E.
createdProgram
Indicates that an entity authored, developed, or produced a particular program (such as software or a coded 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_69a2e7f3aeb48190a19453e3a043f486 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eff0ca408190958405aec2ec6f53 |
completed | Feb. 28, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69a2edecefb081908331ef8b9edf6636 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.