Triple
T34085574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shravana Nakshatra |
E874167
|
entity |
| Predicate | rulingDeity |
P51997
|
FINISHED |
| Object | Vishnu |
—
|
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: Vishnu | Statement: [Shravana Nakshatra, rulingDeity, Vishnu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rulingDeity Context triple: [Shravana Nakshatra, rulingDeity, Vishnu]
-
A.
rulerDeity
Indicates that a deity holds supreme governing or sovereign authority over a realm, people, or cosmic domain.
-
B.
mainDeity
Indicates that one entity serves as the primary or chief deity worshiped, revered, or associated with another entity (such as a religion, temple, or culture).
-
C.
patronDeityOf
chosen
Indicates that one entity serves as the protective or primary deity associated with, worshipped by, or presiding over another entity (such as a person, group, or place).
-
D.
typeOfDeity
Indicates that one entity is classified as a specific kind or category of deity in relation to another.
-
E.
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.
- 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_69f349a61d448190b74642f325d3eb7a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70c0bd8f081908cf39e9ba9919c51 |
completed | May 3, 2026, 8:49 a.m. |
| PD | Predicate disambiguation | batch_69f70ac0170c819098e3b8e41d02efef |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:52 a.m.