Triple
T23845506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vision 2020 for India |
E591107
|
entity |
| Predicate | timeTarget |
P1936
|
FINISHED |
| Object | year 2020 |
—
|
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: year 2020 | Statement: [Vision 2020 for India, timeTarget, year 2020]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeTarget Context triple: [Vision 2020 for India, timeTarget, year 2020]
-
A.
targetTimeGap
Indicates a specified temporal distance or interval that should exist between a reference time and a target time.
-
B.
timeDefinite
Indicates that the associated event or state occurs at a clearly specified, fixed point or interval in time.
-
C.
timeBehind
Indicates that one entity occurs or is positioned later in time than another, lagging behind it on a temporal scale.
-
D.
time
chosen
Indicates a temporal relationship specifying when an event occurs or how entities are ordered or related in time.
-
E.
timeLimited
Indicates that the relationship or action is constrained to occur or remain valid only within a specific, limited 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_69e25d1de32c8190a907afe9c3d6cd6d |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c88b59688190922d6bf329f08721 |
completed | April 29, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f1614612b481908c45d99e588882f9 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:09 p.m.