Triple
T36890310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chalukya of Kalyani |
E911728
|
entity |
| Predicate | notableTempleRegion |
P205105
|
FINISHED |
| Object | Lakkundi |
E911736
|
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: Lakkundi | Statement: [Chalukya of Kalyani, notableTempleRegion, Lakkundi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableTempleRegion Context triple: [Chalukya of Kalyani, notableTempleRegion, Lakkundi]
-
A.
majorTempleLocation
Indicates that a major temple associated with an entity is located at a specified place.
-
B.
hasNotableTemple
Indicates that an entity is associated with a temple that is recognized as particularly important, famous, or significant.
-
C.
notableTemplePatronage
Indicates that an entity is notably recognized for sponsoring, supporting, or endowing a temple or temples.
-
D.
shrineRegion
Indicates that a shrine is located within or associated with a particular geographic region.
-
E.
religiousSiteInRegion
Indicates that a religious site is located within or belongs to a specified geographic region.
- F. None of above. chosen
Provenance (5 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_69f76e8335908190b77e7e11d0e80820 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3e162170708190b24d6042b883af68 |
completed | June 26, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:13 p.m.