Triple
T26514425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | संघ परिवार |
E669772
|
entity |
| Predicate | संबंधित_विचारक |
P28365
|
FINISHED |
| Object | दीनदयाल उपाध्याय |
—
|
NE NERFINISHED |
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.
associatedScholar
chosen
Indicates a relationship where a scholar is linked or connected to another entity (such as a work, institution, or concept) through relevant academic or intellectual involvement.
-
B.
philosophicalRelationTo
Indicates a conceptual or theoretical connection one entity holds toward another within a philosophical framework or viewpoint.
-
C.
associatedTheologian
Indicates a relationship where a theologian is connected or linked to a particular subject, work, institution, or context.
-
D.
discussesThinker
Indicates that one entity engages in discussion or analysis about a particular thinker or philosopher.
-
E.
composerOfRelatedWorks
Indicates that an entity is the composer of works that are related to another specified work or set of works.
- 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_69eeb31b6dcc8190b30632dc3928a0c0 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f61a17a7788190946f7e32d63cd43f |
completed | May 2, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69f611ab768c8190b1849c15a3e59dda |
completed | May 2, 2026, 3 p.m. |
Created at: April 27, 2026, 1:22 a.m.