Triple
T34754671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | عِلِّيِّينَ |
E1001883
|
entity |
| Predicate | تفسير_شائع |
P156529
|
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 the specific type or category of interpretation being applied to something.
-
B.
typicalMeaning
chosen
Indicates that something represents the usual, characteristic, or most common meaning or interpretation associated with something else.
-
C.
commonMeaning
Indicates that multiple entities share the same or very similar meaning or semantic interpretation.
-
D.
frequentlyInterpretedBy
Indicates that an entity is often or regularly interpreted, explained, or given meaning by a particular agent or group.
-
E.
starMeaning
Indicates that one entity represents or conveys the symbolic or interpretive significance of a star associated with 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_69f76db0fb30819096709d43f9a1f45f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.