Triple
T34805585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shyama Kund |
E1003344
|
entity |
| Predicate | hasDivineCounterpart |
P199156
|
FINISHED |
| Object | Radha Kund |
—
|
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: Radha Kund | Statement: [Shyama Kund, hasDivineCounterpart, Radha Kund]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDivineCounterpart Context triple: [Shyama Kund, hasDivineCounterpart, Radha Kund]
-
A.
hasDeity
Indicates that one entity recognizes, worships, or is associated with another entity as its deity or divine figure.
-
B.
hasDivineModel
Indicates that something is patterned after, based on, or derived from a divine or sacred archetype or example.
-
C.
hasFullDivinity
Indicates that an entity possesses complete and unrestricted divine nature or godhood.
-
D.
associatedWithGod
Indicates a relationship in which an entity is linked, related, or connected in some meaningful way to a god or deity.
-
E.
hasViewOnDivinity
Indicates that an entity holds a particular belief, opinion, or perspective regarding divinity or the nature of the divine.
- 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_69f76db600b88190989abdf08fce3b27 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ff234f32888190a1d800a3bda432eb |
completed | May 9, 2026, 12:06 p.m. |
| PD | Predicate disambiguation | batch_69ff228ae9a0819083f4b97c10b923f4 |
completed | May 9, 2026, 12:03 p.m. |
| PDg | Predicate description generation | batch_69ff234e63648190a7b09a161029c8e2 |
completed | May 9, 2026, 12:06 p.m. |
Created at: May 3, 2026, 3:59 p.m.