Triple
T20441940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhind Lok Sabha constituency |
E501415
|
entity |
| Predicate | previousDelimitation |
P65978
|
FINISHED |
| Object | pre-2008 boundaries |
—
|
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: pre-2008 boundaries | Statement: [Bhind Lok Sabha constituency, previousDelimitation, pre-2008 boundaries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousDelimitation Context triple: [Bhind Lok Sabha constituency, previousDelimitation, pre-2008 boundaries]
-
A.
currentDelimitationFrom
Indicates that one entity currently defines or establishes the boundary or extent of another entity.
-
B.
previousCircumscription
chosen
Indicates that one entity served as an earlier or prior version, scope, or boundary definition of another entity.
-
C.
delimitationMethod
Indicates the method or process used to establish or define the boundaries or limits of something.
-
D.
previouslyPartOfBoundaryBetween
Indicates that something once formed part of the dividing line or border between two areas or entities, but no longer does so.
-
E.
divisionSince
Indicates that one entity has been divided or split from another starting at a specific point in time.
- 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_69e0b4ab3cfc8190ac9bf32e932316b1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e685f3b794819080745b135a305ba7 |
completed | April 20, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69e5766df0008190a73c4f613c29678f |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:32 a.m.