Triple
T27896864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meenakshi |
E705515
|
entity |
| Predicate | SundareshwararIsFormOf |
P83904
|
FINISHED |
| Object | Shiva |
—
|
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: Shiva | Statement: [Meenakshi, SundareshwararIsFormOf, Shiva]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SundareshwararIsFormOf Context triple: [Meenakshi, SundareshwararIsFormOf, Shiva]
-
A.
associatedFormOfVishnu
Indicates a relationship where something is linked or connected as a particular form or manifestation of Vishnu.
-
B.
associatedFormOfShiva
chosen
Indicates a relationship where one entity is a particular form, aspect, or manifestation that is traditionally associated with the deity Shiva.
-
C.
TripuraSundariTempleIs
Indicates that something is identified as, or characterized as being, the Tripura Sundari Temple.
-
D.
viewOnAyyaVaikundar
Indicates the perspective, interpretation, or doctrinal stance that an entity holds regarding Ayya Vaikundar.
-
E.
TirumantiramVerseForm
Indicates that a text, statement, or reference is expressed in the specific verse form or metrical style used in the Tirumantiram.
- 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_69ef96b490ac8190a412d04c5d009f3e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f639f5d2588190b87fdb14a487d9d8 |
completed | May 2, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69f6318be69481909d1bcf29b7b60eb2 |
completed | May 2, 2026, 5:17 p.m. |
Created at: April 27, 2026, 6:39 p.m.