Triple
T5323999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | School Breakfast Program |
E121742
|
entity |
| Predicate | becamePermanentProgram |
P10634
|
FINISHED |
| Object | 1975 |
—
|
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: 1975 | Statement: [School Breakfast Program, becamePermanentProgram, 1975]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: becamePermanentProgram Context triple: [School Breakfast Program, becamePermanentProgram, 1975]
-
A.
adoptedProgramme
Indicates that an entity has formally accepted and put into practice a specific programme or plan.
-
B.
establishedProgram
chosen
Indicates that an entity has created and put into operation a formal program that is now in an active, ongoing state.
-
C.
implementedProgram
Indicates that an entity has created, developed, or put into operation a particular program or software system.
-
D.
madeProgram
Indicates that one entity created, developed, or authored a program (such as software or a coded application).
-
E.
formerProgram
Indicates that an entity previously held the role or status of a program but no longer does so.
- 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_69bd463d956c819088105c3db802c017 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd86f20f008190be7b5848af05f2b8 |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd84561c7081909e5937c7816e492c |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 1:59 p.m.