Triple
T21070794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hindu Raj |
E519100
|
entity |
| Predicate | hasDebateAround |
P142728
|
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: [Hindu Raj, hasDebateAround, minority rights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDebateAround Context triple: [Hindu Raj, hasDebateAround, minority rights]
-
A.
hasDebate
Indicates that there is a formal discussion or argument between entities, typically presenting opposing viewpoints on a topic.
-
B.
hasLongTermDebateOn
Indicates that there is an ongoing, extended period of discussion, disagreement, or argument concerning a particular topic or issue.
-
C.
areDebatesOf
Indicates that the subject entities are debates that concern, involve, or are associated with the object entities.
-
D.
hasSourceOfDebate
Indicates that something is the origin or cause of an ongoing disagreement, controversy, or dispute between parties.
-
E.
debatedAs
Indicates that one entity is discussed or argued over in terms of being equivalent to, or serving in the role of, another entity within a debate or comparative argument.
- F. None of above. chosen
Provenance (4 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_69e0b505ef108190b25dd4033e2ff7eb |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6feb8ed4481909c9f804ccd8da3e2 |
completed | April 21, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf9d71881908cd85dfc37db93ca |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2e03d88819086f8b641656ad8b0 |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 2:46 p.m.