Triple
T26062101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mushaf |
E657286
|
entity |
| Predicate | backMatterOftenContains |
P159905
|
FINISHED |
| Object | Tables of divisions (juz’, hizb, etc.) |
—
|
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: Tables of divisions (juz’, hizb, etc.) | Statement: [Mushaf, backMatterOftenContains, Tables of divisions (juz’, hizb, etc.)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: backMatterOftenContains Context triple: [Mushaf, backMatterOftenContains, Tables of divisions (juz’, hizb, etc.)]
-
A.
backDescription
Indicates that an entity provides a description or textual information specifically about the back side or rear view of another entity.
-
B.
backType
Indicates the type or category of a backing or support associated with an entity.
-
C.
hasBackCoverMaterial
Indicates that one entity uses or is made of a specified material for the back cover of an item.
-
D.
coverText
Indicates that one text serves as the cover or front-facing textual representation for another work or resource.
-
E.
backing
Indicates providing support, endorsement, or financial/resources assistance to someone or something, often enabling or strengthening their actions or position.
- F. None of above. chosen
Provenance (4 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_69ee5bbd788481909e22bd7153d0c037 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f606941410819098a15b288273c3e1 |
completed | May 2, 2026, 2:13 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 26, 2026, 7:18 p.m.