Triple
T25693311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tenkalai |
E644253
|
entity |
| Predicate | differsFromVadakalaiIn |
P159186
|
FINISHED |
| Object | interpretation of prapatti |
—
|
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: interpretation of prapatti | Statement: [Tenkalai, differsFromVadakalaiIn, interpretation of prapatti]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: differsFromVadakalaiIn Context triple: [Tenkalai, differsFromVadakalaiIn, interpretation of prapatti]
-
A.
hasDialectalDifferenceWith
Indicates that two language varieties differ from each other in dialectal features such as pronunciation, vocabulary, or grammar.
-
B.
isCulturalDistinction
Indicates that one entity is recognized as a distinguishing cultural feature or marker in comparison to another entity or context.
-
C.
hasDistinctCultureFrom
Indicates that the culture of one entity is different and distinguishable from the culture of another entity.
-
D.
hasVeda
Indicates that an entity possesses, is associated with, or is characterized by a particular Veda.
-
E.
hasVocalStyleComparedTo
Indicates a comparison between entities based on the similarity or resemblance of their vocal style.
- F. None of above. chosen
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_69e77e82c9bc8190893090b2f6c64f1d |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fbc2bcbc81909e16230a8ed01210 |
completed | May 2, 2026, 1:27 p.m. |
| PD | Predicate disambiguation | batch_69f4938262ac8190b41f922d0407d272 |
completed | May 1, 2026, 11:50 a.m. |
| PDg | Predicate description generation | batch_69f497b8abb88190bb672cf6907c4b8d |
completed | May 1, 2026, 12:08 p.m. |
Created at: April 21, 2026, 8:31 p.m.