Triple
T28702481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burari Assembly constituency |
E729590
|
entity |
| Predicate | previousMLATermStartYear |
P193114
|
FINISHED |
| Object | 2015 |
—
|
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: 2015 | Statement: [Burari Assembly constituency, previousMLATermStartYear, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousMLATermStartYear Context triple: [Burari Assembly constituency, previousMLATermStartYear, 2015]
-
A.
previousMPTermEndYear
Indicates the calendar year in which the subject’s immediately preceding term as a Member of Parliament ended.
-
B.
previousMPStartYear
Indicates the year in which the subject’s immediately preceding term as a Member of Parliament began.
-
C.
laterTypeStartYear
Indicates that the starting year of one type or classification occurs later in time than the starting year of another type or classification.
-
D.
matriculationYear
Indicates the calendar year in which an individual formally enrolled or was admitted into an educational program or institution.
-
E.
mlaTermStart
Indicates the date or point in time when a specific term, period, or agreement begins.
- F. None of above. chosen
Provenance (4 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_69f043e6e9688190b6bdd6e5665498ff |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
| PDg | Predicate description generation | batch_69fd389b653c81908a97ab2eff98c6ea |
completed | May 8, 2026, 1:12 a.m. |
Created at: April 28, 2026, 5:43 a.m.