Triple
T26051446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tondaradippodi Alvar |
E647987
|
entity |
| Predicate | writingsAddress |
P265
|
FINISHED |
| Object | Lord Ranganatha as supreme deity |
—
|
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: Lord Ranganatha as supreme deity | Statement: [Tondaradippodi Alvar, writingsAddress, Lord Ranganatha as supreme deity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writingsAddress Context triple: [Tondaradippodi Alvar, writingsAddress, Lord Ranganatha as supreme deity]
-
A.
address
Indicates that one entity directs spoken or written communication specifically to another entity.
-
B.
addressing
Indicates that one entity is directing speech, communication, or attention specifically toward another entity.
-
C.
addresses
chosen
Indicates that one entity directs speech, communication, or written correspondence specifically toward another entity.
-
D.
addressesWork
Indicates that one entity directs or delivers work-related communication or correspondence to another entity.
-
E.
locationAddressed
Indicates that a communication, message, or action is specifically directed to or intended for a particular location or address.
- 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_69e77e8d419481908004e6318d28aaab |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6065ef22881908cecf6defe38519f |
completed | May 2, 2026, 2:12 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 22, 2026, 9:11 a.m.