Triple
T33643633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Food Security Mission |
E861898
|
entity |
| Predicate | startedInPlanPeriod |
P88712
|
FINISHED |
| Object | Eleventh Five Year Plan |
—
|
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: Eleventh Five Year Plan | Statement: [National Food Security Mission, startedInPlanPeriod, Eleventh Five Year Plan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startedInPlanPeriod Context triple: [National Food Security Mission, startedInPlanPeriod, Eleventh Five Year Plan]
-
A.
hasPlanningPeriod
Indicates that an entity is associated with a defined time span allocated for planning activities.
-
B.
recordedInPeriodStart
chosen
Indicates that an event or record began or was first documented at the start of a specified time period.
-
C.
isPlannedThrough
Indicates that something is intended to be achieved, organized, or carried out by means of a specified plan, method, or intermediary process.
-
D.
isSetInTimePeriod
Indicates that an event, story, or situation takes place within a specified time period.
-
E.
appliedDuringPeriod
Indicates that an action, condition, or status was in effect throughout a specified time period.
- 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_69f3498280c48190bcc3494017d14234 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ffc704e1e88190884928a6a5c55a87 |
completed | May 9, 2026, 11:45 p.m. |
| PD | Predicate disambiguation | batch_69ffc6b483d881908ad872e25fa6abc5 |
completed | May 9, 2026, 11:43 p.m. |
Created at: May 1, 2026, 1:42 a.m.