Triple
T12863198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banaras (Varanasi) gharana |
E307647
|
entity |
| Predicate | emphasizesElement |
P17414
|
FINISHED |
| Object | abhinaya |
—
|
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: abhinaya | Statement: [Banaras (Varanasi) gharana, emphasizesElement, abhinaya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emphasizesElement Context triple: [Banaras (Varanasi) gharana, emphasizesElement, abhinaya]
-
A.
positionEmphasized
Indicates that a particular position, stance, or role is given special prominence or stress relative to others.
-
B.
hasEmphasis
chosen
Indicates that one element is given special stress, importance, or prominence relative to others.
-
C.
designEmphasizes
Indicates that a design intentionally places special importance or focus on a particular feature, principle, or aspect over others.
-
D.
emphasizesAttributeOfHermes
Indicates that something highlights or draws special attention to a particular attribute or characteristic of Hermes.
-
E.
highlightsAttributeOf
Indicates that one entity draws attention to, emphasizes, or showcases a particular attribute or property of another entity.
- 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_69d7bdf5e7cc8190be357278bc5ba3bb |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9714208f881908f7f8a921362909a |
completed | April 10, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69d96fa3002881908000357b1f95a3ac |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:37 p.m.