Triple
T24989175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | نظامی گنجوی |
E625401
|
entity |
| Predicate | وابستگی ادبی |
P27711
|
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.
literarySubject
Indicates that one entity serves as the subject, topic, or focus of a literary work created by another entity.
-
C.
literaryAmbition
Indicates that an entity has the desire, intention, or drive to create, achieve, or succeed in the field of literature.
-
D.
inLiterature
chosen
Indicates that a work, concept, or entity is mentioned, discussed, or represented within a piece of literature.
-
E.
literaryInterest
Indicates that one entity has an interest in, appreciation of, or engagement with the literary works or writings 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_69e2ff2611c081908710457fbe6d376b |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:03 a.m.