Triple
T37391475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Periyanayaki |
E928721
|
entity |
| Predicate | languageRegionOfWorship |
P23627
|
FINISHED |
| Object | Tamil-speaking regions |
—
|
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: Tamil-speaking regions | Statement: [Periyanayaki, languageRegionOfWorship, Tamil-speaking regions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageRegionOfWorship Context triple: [Periyanayaki, languageRegionOfWorship, Tamil-speaking regions]
-
A.
languageOfWorship
Indicates the language in which religious worship, rituals, or liturgical practices are conducted.
-
B.
majorRegionOfWorship
chosen
Indicates the primary geographic region where a deity, religion, or cult is predominantly worshipped.
-
C.
languageOfReligion
Indicates the language in which a particular religion is traditionally expressed, practiced, or documented.
-
D.
liturgicalUseRegion
Indicates the geographic region or area in which a particular liturgical practice, text, or usage is observed or applied.
-
E.
laterReligionRegionOf
Indicates that a region became associated with a particular religion at a later time than another referenced region or context.
- 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_69f76ebb10c481909b54b9dba263e29f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a0191d96dc88190ac0823e534f9d704 |
completed | May 11, 2026, 8:22 a.m. |
| PD | Predicate disambiguation | batch_6a01908110448190a46442ffe4d15f5f |
completed | May 11, 2026, 8:17 a.m. |
Created at: May 3, 2026, 4:16 p.m.