Triple
T29047275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | نقشِ فریادی |
E735167
|
entity |
| Predicate | ادبی_روایت |
P36841
|
FINISHED |
| Object | کلاسیکی اردو شاعری |
—
|
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: کلاسیکی اردو شاعری | Statement: [نقشِ فریادی, ادبی_روایت, کلاسیکی اردو شاعری]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ادبی_روایت Context triple: [نقشِ فریادی, ادبی_روایت, کلاسیکی اردو شاعری]
-
A.
literaryMuseOf
Indicates a relationship in which one entity serves as the creative inspiration or muse for another entity’s literary work.
-
B.
literaryAmbition
Indicates that an entity has the desire, intention, or drive to create, achieve, or succeed in the field of literature.
-
C.
fieldOfWriting
Indicates that one entity is the domain, genre, or subject area in which another entity writes or produces written work.
-
D.
literaryAuthor
Indicates that one entity is the author or writer of a literary work represented by the other entity.
-
E.
literarySubject
chosen
Indicates that one entity serves as the subject, topic, or focus of a literary work created by 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_69f077e64b88819094d37bdbca8191b3 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f66062f54481908eedcc2f2a11295a |
completed | May 2, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 10:06 a.m.