Triple
T35576165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kishanganj Lok Sabha constituency |
E1028079
|
entity |
| Predicate | dominantIssues |
P57423
|
FINISHED |
| Object | minority rights |
—
|
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: minority rights | Statement: [Kishanganj Lok Sabha constituency, dominantIssues, minority rights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominantIssues Context triple: [Kishanganj Lok Sabha constituency, dominantIssues, minority rights]
-
A.
primaryIssue
chosen
Indicates that the related item is the main or most important issue among a set of issues.
-
B.
mainTitleIssues
Indicates that there are problems or concerns specifically related to the main title of an item, work, or record.
-
C.
issues
Indicates that an entity formally produces, releases, or distributes something, such as a document, order, or resource, making it officially available.
-
D.
majorIssue
Indicates that something is a primary or most significant problem, concern, or obstacle in a given context.
-
E.
underlyingIssue
Indicates that one situation, problem, or condition is the fundamental cause or root problem behind another.
- 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_69f76e0386688190b931bacdc145938c |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:04 p.m.