Triple
T12805943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaipur gharana |
E306143
|
entity |
| Predicate | stylisticFocus |
P106479
|
FINISHED |
| Object | layakari (rhythmic play) |
—
|
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: layakari (rhythmic play) | Statement: [Jaipur gharana, stylisticFocus, layakari (rhythmic play)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stylisticFocus Context triple: [Jaipur gharana, stylisticFocus, layakari (rhythmic play)]
-
A.
stylisticRange
Indicates the range or spectrum of styles that characterize or can be applied to something.
-
B.
rhetoricalStyle
Indicates the characteristic manner or technique of expression used in communication, such as tone, structure, and persuasive strategies.
-
C.
poeticStyle
Indicates the stylistic or formal manner in which something is expressed in poetry, such as its structure, tone, and linguistic features.
-
D.
marksStylisticShiftFrom
Indicates that one element signals a change in style, tone, or manner relative to another element.
-
E.
writingFocus
Indicates that an entity’s primary attention or effort is directed toward writing or written expression.
- 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_69d7bdf366888190a8cccb982606889c |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e7f370c8190b3fc39c1b63394c6 |
completed | April 10, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69d9640ed7448190b276e7fab649f7d2 |
completed | April 10, 2026, 8:56 p.m. |
| PDg | Predicate description generation | batch_69d96d88be0481908c311f1e71b61e70 |
completed | April 10, 2026, 9:37 p.m. |
Created at: April 9, 2026, 5:31 p.m.