Triple
T13157585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ghaziabad Lok Sabha constituency |
E312629
|
entity |
| Predicate | currentMPTermStart |
P81949
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [Ghaziabad Lok Sabha constituency, currentMPTermStart, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentMPTermStart Context triple: [Ghaziabad Lok Sabha constituency, currentMPTermStart, 2014]
-
A.
firstTermStart
Indicates that an entity marks the starting point or initial term in an ordered sequence, period, or agreement.
-
B.
startDateOfCurrentTermLength
chosen
Indicates the calendar date on which the currently active term or period of a defined duration begins.
-
C.
mlaTermStart
Indicates the date or point in time when a specific term, period, or agreement begins.
-
D.
nextTermStartDate
Indicates the date on which the next term or period in a sequence is scheduled to begin.
-
E.
earlierMPStartDate
Indicates that one entity’s MP start date occurs earlier in time than another entity’s MP start 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_69d806aabde48190899e13e41659cae5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bbd1d088190b7c69f37fc6eeb64 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:12 p.m.