Triple
T14047319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vedavalli Thayar |
E337990
|
entity |
| Predicate | honorificTitle |
P2097
|
FINISHED |
| Object | Thayar |
E1076167
|
NE 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: Thayar | Statement: [Vedavalli Thayar, honorificTitle, Thayar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Thayar Context triple: [Vedavalli Thayar, honorificTitle, Thayar]
-
A.
Thayar
chosen
Thayar is a revered Hindu mother goddess, especially honored in Sri Vaishnavism as the compassionate consort of Lord Vishnu.
-
B.
Thaya
Thaya is a river in Central Europe that flows through Austria and the Czech Republic, forming part of the border between the two countries.
-
C.
Thara
Thara is an alternate name or variant of Terah, a biblical figure known as the father of Abraham.
-
D.
Thasra
Thasra is a town located in the Kheda district of the Indian state of Gujarat.
-
E.
Thavil
Thavil is a traditional South Indian barrel-shaped percussion instrument, central to Tamil temple and folk music, typically played with sticks and fingers alongside the nadaswaram.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d81c664e48819088cbd8f433aeffe5 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de3c88b5e48190b0f0149102c08992 |
completed | April 14, 2026, 1:09 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcb65c1a90819097754497f07f5312 |
completed | May 7, 2026, 3:57 p.m. |
Created at: April 9, 2026, 10:20 p.m.