Triple
T31645329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adi tala |
E807569
|
entity |
| Predicate | hasDrutamAksharas |
P172604
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Adi tala, hasDrutamAksharas, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDrutamAksharas Context triple: [Adi tala, hasDrutamAksharas, 2]
-
A.
hasGranthaConsonants
Indicates that an entity includes or makes use of consonant characters from the Grantha script.
-
B.
hasVirama
Indicates that a character or script element is associated with a virama sign, typically used to suppress the inherent vowel or join consonants in abugida writing systems.
-
C.
hasViramaSign
Indicates that a character or script element is associated with, or takes, a virama sign used to suppress the inherent vowel in abugida writing systems.
-
D.
usesSwaras
Indicates that one entity employs or incorporates specific musical notes (swaras) in relation to another entity or context.
-
E.
hasMatrasPerVibhag
Indicates a relationship where each vibhag (metrical division) is associated with a specific number of matras (time units) it contains.
- 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_69f348d9ce58819093ea2da83cbeeec1 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6ac1ed23c8190ace57ffc9d8a3dc6 |
completed | May 3, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aba8fba48190bc1a17117244cae1 |
completed | May 3, 2026, 1:58 a.m. |
Created at: April 30, 2026, 10:50 p.m.