Triple
T11259471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thrifty Food Plan |
E266523
|
entity |
| Predicate | 2021RevisionBasis |
P84003
|
FINISHED |
| Object | updated dietary guidelines |
—
|
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: updated dietary guidelines | Statement: [Thrifty Food Plan, 2021RevisionBasis, updated dietary guidelines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 2021RevisionBasis Context triple: [Thrifty Food Plan, 2021RevisionBasis, updated dietary guidelines]
-
A.
revisionOf
Indicates that one entity is a modified or updated version of another earlier entity.
-
B.
previouslyBasedOn
Indicates that something was formerly derived from, adapted from, or dependent on another source, but is no longer based on it in its current state.
-
C.
revisedByStandard
chosen
Indicates that something has been updated or modified in accordance with a specified standard or set of standards.
-
D.
planningBasis
Indicates that one entity serves as the foundational reference or justification used by another entity when making plans or preparing actions.
-
E.
dateRevisedTo
Indicates that an entity’s date has been updated or changed to a new specified date.
- 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_69d6aac7953c8190b82caf9d7640fdf9 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e936cb048190b4d6fb2851ef8932 |
completed | April 9, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69d78793c00481908a3f764b610b77a4 |
completed | April 9, 2026, 11:03 a.m. |
Created at: April 8, 2026, 9:31 p.m.