Triple
T29211974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Srivilliputhur Andal Temple |
E740568
|
entity |
| Predicate | associatedPoetSaint |
P43509
|
FINISHED |
| Object | Andal |
E202433
|
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: Andal | Statement: [Srivilliputhur Andal Temple, associatedPoetSaint, Andal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedPoetSaint Context triple: [Srivilliputhur Andal Temple, associatedPoetSaint, Andal]
-
A.
poetAssociated
Indicates a relationship where a poet is connected or linked to another entity, such as a work, place, movement, or person, through relevance, collaboration, influence, or affiliation.
-
B.
collectiveNameOfPoetSaints
Indicates a naming relationship where a term denotes the collective group of poet-saints.
-
C.
linkedToSaint
chosen
Indicates that one entity has a direct association or connection with a saint.
-
D.
associatedWithPoem
Indicates a relationship in which an entity is connected or linked to a particular poem, such as by authorship, subject, reference, or contextual association.
-
E.
devotionalPoets
Indicates a relationship in which poets are characterized by or associated with devotional (religious or spiritual) themes in their work.
- F. None of above.
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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_6a033029023481909d9fa4a76b954879 |
completed | May 12, 2026, 1:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a25a847fc208190b1ed19a536b1663c |
completed | June 7, 2026, 5:20 p.m. |
| PD | Predicate disambiguation | batch_6a032d9f1fa48190bd1c94a8f930d02c |
completed | May 12, 2026, 1:39 p.m. |
Created at: April 28, 2026, 12:11 p.m.