Triple
T19548127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Varadaraja Perumal |
E489127
|
entity |
| Predicate | connectedToLegend |
P1582
|
FINISHED |
| Object | legend of Brahma’s yagna at Kanchipuram |
—
|
LITERAL FINISHED |
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: legend of Brahma’s yagna at Kanchipuram | Statement: [Varadaraja Perumal, connectedToLegend, legend of Brahma’s yagna at Kanchipuram]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedToLegend Context triple: [Varadaraja Perumal, connectedToLegend, legend of Brahma’s yagna at Kanchipuram]
-
A.
hasLegendAssociatedWith
chosen
Indicates that something is connected to or accompanied by a traditional story, myth, or legend.
-
B.
inLegendRole
Indicates that an entity appears in a legendary or mythic context fulfilling a specific narrative or symbolic role.
-
C.
instrumentInLegend
Indicates that an instrument is featured or plays a role within a legend or mythological narrative.
-
D.
connectedLine
Indicates that two entities are joined by a continuous line or linear connection.
-
E.
regionOfLegend
Indicates the geographic area or locale with which a particular legend or myth is associated.
- 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_69d8e8db5b6c8190984b61f91981f575 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63d2e5e588190ac3a6f612d4fb54b |
completed | April 20, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69e514d4df3c8190b7e9b3b4fdf9452a |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:41 p.m.