Triple
T15577682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | سورة لهب |
E374409
|
entity |
| Predicate | تُنسب إلى |
P95181
|
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.
assignedTo
Indicates that responsibility for a task, item, or role has been designated to a specific entity.
-
B.
traditionallyAssignedTo
chosen
Indicates that something is customarily or historically designated as the responsibility, role, or domain of a particular entity according to tradition.
-
C.
notablyAssociatedWith
Indicates that one entity is prominently or distinctively connected with another in a way that is especially noteworthy or remarkable.
-
D.
assignedToWorkBy
Indicates that one entity is designated or directed by another entity to perform a specific job, task, or role.
-
E.
allottedTo
Indicates that something has been assigned or allocated to a particular entity as its designated recipient or user.
- 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_69d85ccd575081908909b71a3f3e3a61 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e22c89081909b1ec0cd36a1ef45 |
completed | April 16, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69deda817e9881909b0c66fc9056f7d5 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:11 a.m.