Triple
T26514417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | संघ परिवार |
E669772
|
entity |
| Predicate | धार्मिक_सम्बंध |
P142283
|
FINISHED |
| Object | हिंदू धर्म |
E3461
|
NE 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.
devotionalRelationship
Indicates a relationship in which one entity expresses deep religious or spiritual devotion, reverence, or worship toward another entity.
-
B.
धर्म से संबंध
chosen
Indicates a relationship in which one entity is connected or related to another through religion or religious affiliation.
-
C.
hasReligious
Indicates that an entity is associated with, practices, or adheres to a particular religion or religious affiliation.
-
D.
associatedReligionOrBelief
Indicates that an entity is connected to, identified with, or characterized by a particular religion or belief system.
-
E.
relationshipToReligion
Indicates the nature or type of connection an entity has to a religion, such as affiliation, stance, or involvement.
- F. None of above.
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_69eeb31b6dcc8190b30632dc3928a0c0 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f61394b50c81909e628b2e5b1aa3d5 |
completed | May 2, 2026, 3:09 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a11c80dda5081909b268a35fd4bde1c |
completed | May 23, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:22 a.m.