Triple
T9699873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Syama Sastri |
E234746
|
entity |
| Predicate | musicalFormUsed |
P6683
|
FINISHED |
| Object | kriti |
—
|
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: kriti | Statement: [Syama Sastri, musicalFormUsed, kriti]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicalFormUsed Context triple: [Syama Sastri, musicalFormUsed, kriti]
-
A.
hasMusicalForm
chosen
Indicates that one entity (typically a musical work or piece) is characterized by or structured according to a particular musical form.
-
B.
usesMusicalElement
Indicates that one entity employs or incorporates a particular musical element (such as rhythm, melody, harmony, or timbre) in its composition, performance, or structure.
-
C.
partOfMusical
Indicates that something is a component, segment, or element belonging to a larger musical work or performance.
-
D.
usesMusicalSystem
Indicates that one entity employs or operates according to a particular musical system, framework, or set of musical rules.
-
E.
musicalFunction
Indicates the specific role or function an entity plays within a musical context, such as its harmonic, structural, or performative purpose in a piece or performance.
- 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_69ca84cb580c8190a7e5f4b3bcdaf2a4 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9d6eab0c8190abac1b009d625975 |
completed | April 1, 2026, 10:34 p.m. |
| PD | Predicate disambiguation | batch_69cd03b641408190942464eaf174c6b5 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:18 p.m.