Triple
T30215016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sundararaja Perumal |
E768179
|
entity |
| Predicate | isAssociatedWithTemple |
P13905
|
FINISHED |
| Object | Alagar Kovil |
—
|
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: Alagar Kovil | Statement: [Sundararaja Perumal, isAssociatedWithTemple, Alagar Kovil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAssociatedWithTemple Context triple: [Sundararaja Perumal, isAssociatedWithTemple, Alagar Kovil]
-
A.
associatedTemple
chosen
Indicates a relationship where one entity is linked or connected to a particular temple, typically as its relevant or related religious site.
-
B.
associatedWithTempleComplex
Indicates a relationship in which an entity is connected or related to a specific temple complex, such as by location, function, use, or historical association.
-
C.
associatedWithTempleTown
Indicates a relationship where an entity has a connection or linkage to a town that is characterized by or centered around a temple.
-
D.
hasTempleOf
Indicates that a location or entity possesses, contains, or is the site of a temple dedicated to a particular deity, figure, or purpose.
-
E.
residesInTemple
Indicates that one entity lives or dwells within a temple associated with another entity.
- 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_69f2247fd8b8819087fcf83cb7a05eb8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67ff517908190ad290edafd6c6f5f |
completed | May 2, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:33 p.m.