Triple
T6768148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ambala Lok Sabha constituency |
E154774
|
entity |
| Predicate | delimitationYear |
P46007
|
FINISHED |
| Object | 2008 |
—
|
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: 2008 | Statement: [Ambala Lok Sabha constituency, delimitationYear, 2008]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: delimitationYear Context triple: [Ambala Lok Sabha constituency, delimitationYear, 2008]
-
A.
basedOnCensusYear
Indicates that something (such as data, a decision, or a classification) is derived from or determined using information from a specific census year.
-
B.
divisionYear
Indicates the year in which a division or split of an entity took place.
-
C.
lastDelimitationYear
chosen
Indicates the year in which the most recent boundary or delimitation of the entity was officially established or updated.
-
D.
populationCensusYear
Indicates the specific year in which an official population census was conducted or recorded for an entity.
-
E.
notableRedistrictingYear
Indicates that a given year is recognized as significant for redistricting activities, such as major changes to electoral district boundaries.
- 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_69c688109c1c8190added9a221292af0 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d231b79c81908a4f7fa8f253706d |
completed | March 27, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69c6d094105881909c5806eb4afa6306 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:12 p.m.