Triple
T38125403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hill Rajas |
E952053
|
entity |
| Predicate | opposedReligiousGroup |
P195571
|
FINISHED |
| Object | Sikh community |
—
|
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: Sikh community | Statement: [Hill Rajas, opposedReligiousGroup, Sikh community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposedReligiousGroup Context triple: [Hill Rajas, opposedReligiousGroup, Sikh community]
-
A.
opposedReligiousPolicyOf
Indicates that one entity actively disagreed with and resisted the religious policy or policies established or supported by another entity.
-
B.
religiousCounterpart
Indicates that one entity serves as the religious equivalent or analogue of another entity within a different belief system or tradition.
-
C.
ethnicOrReligiousGroup
Indicates that one entity is an ethnic or religious group to which the other entity belongs or with which it is associated.
-
D.
religiousGroupMentioned
Indicates that a religious group is referenced or mentioned in the given context or statement.
-
E.
religiousAlliance
Indicates a cooperative relationship formed between entities based on shared religious beliefs, institutions, or objectives.
- 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_69f76f083548819082bd2bbf53c79e8e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fdd92396788190ae1424bc1ae55844 |
completed | May 8, 2026, 12:37 p.m. |
| PD | Predicate disambiguation | batch_69fdd678f40481909a717a2daec83b36 |
completed | May 8, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69fdd922d73c81908ad3faade247ec16 |
completed | May 8, 2026, 12:37 p.m. |
Created at: May 3, 2026, 4:21 p.m.