Triple
T21240455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bahujan Samaj Party |
E523454
|
entity |
| Predicate | hasStrongBaseAmong |
P60372
|
FINISHED |
| Object | Dalits in Uttar Pradesh |
—
|
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: Dalits in Uttar Pradesh | Statement: [Bahujan Samaj Party, hasStrongBaseAmong, Dalits in Uttar Pradesh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStrongBaseAmong Context triple: [Bahujan Samaj Party, hasStrongBaseAmong, Dalits in Uttar Pradesh]
-
A.
hasMajorBaseAmong
Indicates that one entity has its primary or most significant base of operations located within or among another entity or group.
-
B.
hasSupportBaseIn
chosen
Indicates that one entity maintains an operational or organizational base of support located in another entity.
-
C.
hasMassBaseAmong
Indicates that one entity possesses a fundamental or baseline mass value when considered among a specified group or context.
-
D.
hasSecondaryBase
Indicates that an entity possesses or is associated with a secondary or additional base, distinct from its primary base.
-
E.
hasBaseCount
Indicates the number of base units or fundamental components associated with an entity.
- 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_69e0b513b89c81908b27147e91368db2 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e735239f48819091ffe518b1aed2e8 |
completed | April 21, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69e5f60e1a888190ba75e2e900270a4e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:46 p.m.