Triple
T26980301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brihadeeswara |
E679583
|
entity |
| Predicate | isPresidingDeityOf |
P7648
|
FINISHED |
| Object | Rajarajeswaram |
—
|
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: Rajarajeswaram | Statement: [Brihadeeswara, isPresidingDeityOf, Rajarajeswaram]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPresidingDeityOf Context triple: [Brihadeeswara, isPresidingDeityOf, Rajarajeswaram]
-
A.
mainDeity
chosen
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).
-
B.
typeOfDeity
Indicates that one entity is classified as a specific kind or category of deity in relation to another.
-
C.
hasSupremeDeityRole
Indicates that an entity holds the highest divine or ultimate god role within a religious or mythological hierarchy.
-
D.
hasDeity
Indicates that one entity recognizes, worships, or is associated with another entity as its deity or divine figure.
-
E.
hasConsortDeity
Indicates that one deity is the consort (spouse or intimate divine partner) of another 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_69eeeb507a7081909d516e1fa08b7d29 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f621565a3c8190ba5ede5ab86328af |
completed | May 2, 2026, 4:07 p.m. |
| PD | Predicate disambiguation | batch_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 6:45 a.m.