Triple
T31645331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adi tala |
E807569
|
entity |
| Predicate | totalMatras |
P155655
|
FINISHED |
| Object | 8 |
—
|
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: 8 | Statement: [Adi tala, totalMatras, 8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: totalMatras Context triple: [Adi tala, totalMatras, 8]
-
A.
hasMatraCount
chosen
Indicates that an entity (such as a word or syllable) is associated with a specific number of matras (metrical time units or beats).
-
B.
hasMatrasPerVibhag
Indicates a relationship where each vibhag (metrical division) is associated with a specific number of matras (time units) it contains.
-
C.
hasMatraPerVibhag
Indicates a relationship where each rhythmic division (vibhag) is associated with a specified number or pattern of matras (beats) within a metric structure.
-
D.
hasDrutamAksharas
Indicates that something possesses or is associated with a specific number of drutam rhythmic units (aksharas) in a metrical or musical context.
-
E.
usesSwaras
Indicates that one entity employs or incorporates specific musical notes (swaras) in relation to another entity 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_69f348d9ce58819093ea2da83cbeeec1 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 30, 2026, 10:50 p.m.