Triple
T19143236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jabalpur Lok Sabha constituency |
E468609
|
entity |
| Predicate | currentMPTerm |
P69740
|
FINISHED |
| Object | 17th Lok Sabha |
—
|
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: 17th Lok Sabha | Statement: [Jabalpur Lok Sabha constituency, currentMPTerm, 17th Lok Sabha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentMPTerm Context triple: [Jabalpur Lok Sabha constituency, currentMPTerm, 17th Lok Sabha]
-
A.
currentMP
chosen
Indicates that the subject is the person who currently serves as a Member of Parliament representing the object’s constituency or jurisdiction.
-
B.
currentMSP
Indicates that an entity is the managed service provider (MSP) that is currently active or in effect for another entity.
-
C.
positionTerm
Indicates that one entity holds, is assigned, or is described by a specific role, title, or positional designation in relation to another entity.
-
D.
currentName
Indicates the present or most recently assigned name associated with an entity.
-
E.
currentClassification
Indicates the present category or status that has been assigned to an entity at this 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_69d8dd0796a48190b34ce4cd9d3f3be5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e976e340819098efccc30b2eef0e |
completed | April 20, 2026, 8:53 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b475d88190a8c15e8eb01dbfef |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:05 p.m.