Triple
T5049463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kanchipuram |
E113747
|
entity |
| Predicate | hasNumberOfDivyaDesams |
P60871
|
FINISHED |
| Object | 14 |
—
|
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: 14 | Statement: [Kanchipuram, hasNumberOfDivyaDesams, 14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfDivyaDesams Context triple: [Kanchipuram, hasNumberOfDivyaDesams, 14]
-
A.
isDivyaDesam
Indicates that a location is one of the 108 sacred Vishnu temples (Divya Desams) revered in the Tamil Vaishnavite tradition.
-
B.
hasJyotirlingaStatus
Indicates that something holds the religious designation or status of a Jyotirlinga within the context of Hindu worship.
-
C.
hasNumberOfDeities
Indicates the specific count of deities associated with an entity, such as a religion, mythology, or belief system.
-
D.
isPancharangaKshetram
Indicates that a temple or sacred site is recognized as one of the Pancharanga Kshetrams, the five traditional holy shrines dedicated to Lord Ranganatha (Vishnu) along the Kaveri river.
-
E.
numberOfHinduCaves
Indicates the quantity of caves that are identified or classified as Hindu caves in relation to a given subject.
- 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_69bd44391fc48190a311ce9c826c209b |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74249a8c8190952680aee06a9286 |
completed | March 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69bd715479f08190933604aebd34414f |
completed | March 20, 2026, 4:09 p.m. |
| PDg | Predicate description generation | batch_69bd73089f548190834103366e24ab40 |
completed | March 20, 2026, 4:17 p.m. |
Created at: March 20, 2026, 1:37 p.m.