Triple
T31645222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arabhi |
E807567
|
entity |
| Predicate | melakartaParent |
P172044
|
FINISHED |
| Object | Shankarabharanam |
—
|
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: Shankarabharanam | Statement: [Arabhi, melakartaParent, Shankarabharanam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: melakartaParent Context triple: [Arabhi, melakartaParent, Shankarabharanam]
-
A.
hasNumberOfTithis
Indicates the relationship that specifies how many tithis (lunar days) are associated with a given entity or period.
-
B.
monthInHinduCalendar
Indicates that a specified time or event falls within a particular month as defined by the Hindu calendar system.
-
C.
positionInSaptarishi
Indicates the specific place or ordering that an entity occupies within the Saptarishi group.
-
D.
RahuAndKetuType
Indicates a relationship or classification involving the astrological entities Rahu and Ketu, specifying how they are jointly characterized or typed in a given context.
-
E.
occursOnNakshatra
Indicates that an event or phenomenon takes place during, or is associated with, a specific nakshatra (lunar mansion) in the traditional Indian astronomical/astrological system.
- 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_69f348d9ce58819093ea2da83cbeeec1 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a956e9b08190bf83547bba8e8147 |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a757c6e081908e37631e5d8d246b |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a8036ab481908019f2f071fa406e |
completed | May 3, 2026, 1:42 a.m. |
Created at: April 30, 2026, 10:50 p.m.