Triple
T23850201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | سعدینامه |
E592139
|
entity |
| Predicate | سبک بیان |
P35511
|
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.
rhetoricalStyle
chosen
Indicates the characteristic manner or technique of expression used in communication, such as tone, structure, and persuasive strategies.
-
B.
spokenVsWritten
Indicates that the relationship contrasts or distinguishes between spoken and written forms of the same content or expression.
-
C.
سبک
Indicates a stylistic relationship, where one entity is characterized by, associated with, or exemplifies a particular style or manner of expression in relation to another.
-
D.
commentarialStyle
Indicates the manner or approach taken in writing or presenting commentary on a text, event, or subject.
-
E.
languageModality
Indicates the mode or form in which a language is expressed or perceived (e.g., spoken, signed, written, or tactile).
- 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_69e25d221d908190b9b502ad31e66a3f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c986f7e08190a6d361423946ff05 |
completed | April 29, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f1614612b481908c45d99e588882f9 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:11 p.m.