Triple
T30818148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | السنة النبوية |
E784841
|
entity |
| Predicate | وظيفتها |
P153140
|
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.
purposeOfWork
Indicates that one entity is the intended goal, function, or objective that motivates or justifies the work performed by another entity.
-
B.
settingOfWork
Indicates the place, time, or environment in which a creative work’s narrative or events are situated.
-
C.
rolePurpose
chosen
Indicates the intended function, objective, or responsibility that a given role is meant to fulfill.
-
D.
usedInWorkBy
Indicates that something (such as a method, material, or concept) is employed or incorporated within a work created by a particular agent or author.
-
E.
designationUse
Indicates how a particular designation or title is intended to be used or applied in relation to an 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_69f224b4eda48190bd212ce4f3901e56 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6906ad50481909a700664e0b70fb0 |
completed | May 3, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:44 p.m.