Triple
T24056602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | سعدی شیرازی |
E595823
|
entity |
| Predicate | وابستگی فرهنگی |
P145610
|
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.
پیوستگی فرهنگی
Indicates a relationship where entities share, maintain, or contribute to a continuous and cohesive cultural connection or tradition.
-
B.
culturalType
Indicates the classification of something according to its cultural category, style, or tradition.
-
C.
culturalEmphasis
Indicates that a culture, group, or context places particular importance or priority on a specific value, practice, or domain.
-
D.
culturalCategory
Indicates that one entity classifies or groups another entity according to a particular culture, tradition, or culturally defined type.
-
E.
isPartOfCulturalDomain
chosen
Indicates that something belongs to, falls within, or is associated with a particular cultural sphere, tradition, or domain.
- 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_69e288c184b081909f1f1751fb8e299a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1da50d6108190a36bffaa475c8b93 |
completed | April 29, 2026, 10:15 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:32 p.m.