Triple
T20071990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kashmir school of poetics |
E499759
|
entity |
| Predicate | viewOfPoetry |
P77792
|
FINISHED |
| Object | poetry as vehicle of aesthetic rasa |
—
|
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: poetry as vehicle of aesthetic rasa | Statement: [Kashmir school of poetics, viewOfPoetry, poetry as vehicle of aesthetic rasa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewOfPoetry Context triple: [Kashmir school of poetics, viewOfPoetry, poetry as vehicle of aesthetic rasa]
-
A.
viewsPoetryAs
chosen
Indicates that one entity regards or interprets poetry in a particular way or from a specific perspective.
-
B.
readPoemAt
Indicates that an entity reads or performs a poem at a specific time, place, or event.
-
C.
poem
Indicates that one entity is a poem created, authored, or associated with another entity.
-
D.
poeticStructure
Indicates a relationship where one entity defines, embodies, or specifies the formal poetic organization (such as meter, rhyme scheme, or stanza pattern) used by another entity.
-
E.
containsPoem
Indicates that one entity includes or holds a poem as part of its contents.
- 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_69da627770948190997f486f9a2e370f |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66438633481908710907c48806499 |
completed | April 20, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69e54cf369b88190931532420517dac7 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:40 p.m.