Triple
T31358201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Radha Gopinath |
E799793
|
entity |
| Predicate | deityAspectOf |
P73550
|
FINISHED |
| Object | Radha |
—
|
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 | Statement: [Radha Gopinath, deityAspectOf, Radha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deityAspectOf Context triple: [Radha Gopinath, deityAspectOf, Radha]
-
A.
hasDeityAspect
chosen
Indicates that one entity embodies, represents, or functions as a specific divine aspect or manifestation of another deity.
-
B.
emphasizesAspectOfDeity
Indicates that one entity highlights, stresses, or draws special attention to a particular attribute, role, or dimension of a deity.
-
C.
deityIdentification
Indicates that one entity is identified, recognized, or designated as a deity in relation to another entity or context.
-
D.
roleOfReferencedDeity
Indicates that one entity specifies the function, status, or position held by a deity that is referenced in relation to another entity or context.
-
E.
attributeOfDeity
Indicates that something is a characteristic, quality, or property belonging to a deity.
- 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_69f224e5e9bc8190a16339328897c4f8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69f4900b88190872299a7ec7e7674 |
completed | May 3, 2026, 1:05 a.m. |
| PD | Predicate disambiguation | batch_69f69d1d25e88190a7f57d323574da90 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:17 p.m.