Triple
T26508308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allahabad Lok Sabha constituency |
E669610
|
entity |
| Predicate | delimitationAffectedIn |
P160803
|
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: [Allahabad Lok Sabha constituency, delimitationAffectedIn, 2008]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: delimitationAffectedIn Context triple: [Allahabad Lok Sabha constituency, delimitationAffectedIn, 2008]
-
A.
delimitationImpact
Indicates the effect that a boundary-setting or demarcation process has on the entities or conditions involved.
-
B.
delimitationCompleted
Indicates that the process of defining and establishing clear boundaries or limits between entities has been fully completed.
-
C.
delimitationBody
Indicates the boundary or extent of something, specifying the limits that define where it begins and ends.
-
D.
delimitationBodyEstablishedBy
Indicates that a boundary or delimitation body was formally created or set up by a specified agent or authority.
-
E.
delimitationMethod
Indicates the method or process used to establish or define the boundaries or limits of something.
- 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_69eeb319ec70819090834c2591cf5f1e |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6138fa6e881908d60d7d354ee2b4e |
completed | May 2, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69f604120e848190b516c29b781d19cc |
completed | May 2, 2026, 2:02 p.m. |
Created at: April 27, 2026, 1:18 a.m.