Triple
T7531743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | राष्ट्रीय स्वयंसेवक संघ |
E178037
|
entity |
| Predicate | विवाद |
P1783
|
FINISHED |
| Object | सांप्रदायिकता के आरोप |
—
|
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: सांप्रदायिकता के आरोप | Statement: [राष्ट्रीय स्वयंसेवक संघ, विवाद, सांप्रदायिकता के आरोप]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: विवाद Context triple: [राष्ट्रीय स्वयंसेवक संघ, विवाद, सांप्रदायिकता के आरोप]
-
A.
controversy
chosen
Indicates a situation in which there is active disagreement, dispute, or public debate between parties over a particular issue, action, or claim.
-
B.
disputed
Indicates that there is active disagreement or contestation over the validity, ownership, interpretation, or status of the relationship or claim between the entities.
-
C.
controversialBecause
Indicates that one entity is considered controversial specifically due to, or as a result of, its relationship with or association to another entity.
-
D.
controversyType
Indicates the specific kind or category of controversy associated with an entity or situation.
-
E.
contestedBy
Indicates that one party challenges, disputes, or opposes a claim, decision, or position held by another party.
- 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_69c69f2acdbc8190b5a8320168c1d0ba |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f84753fc81908bee2013004ef5fb |
completed | March 27, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d8eedc81908c1ae421e0e63798 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:47 p.m.