Triple
T31645501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sri Rama of Tiruvaiyaru |
E807572
|
entity |
| Predicate | epicAssociation |
P138043
|
FINISHED |
| Object | Ramayana |
—
|
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: Ramayana | Statement: [Sri Rama of Tiruvaiyaru, epicAssociation, Ramayana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: epicAssociation Context triple: [Sri Rama of Tiruvaiyaru, epicAssociation, Ramayana]
-
A.
associatedWithEpicTheme
Indicates that something is connected or related to a particular epic theme, such as a major storyline, motif, or overarching narrative focus.
-
B.
associatedEpicHero
chosen
Indicates a relationship where one entity is linked to, or thematically connected with, a particular epic hero.
-
C.
associatedEpicCycle
Indicates that one entity is linked to, or forms part of, a particular epic cycle within a larger narrative or project structure.
-
D.
associatedEpicEvent
Indicates that one entity is linked or connected to a particular epic event in a relevant or meaningful way.
-
E.
associatedEpicTradition
Indicates a relationship where something is linked to, derived from, or belongs within a particular epic tradition or body of epic narratives.
- 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_69f348d9ce58819093ea2da83cbeeec1 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a91e4f4c8190831089d81f5f0026 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a757c6e081908e37631e5d8d246b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:50 p.m.