Triple
T7902630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juz 16 |
E183491
|
entity |
| Predicate | isEqualDivisionWith |
P10893
|
FINISHED |
| Object | other 29 ajza of the Quran |
—
|
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: other 29 ajza of the Quran | Statement: [Juz 16, isEqualDivisionWith, other 29 ajza of the Quran]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEqualDivisionWith Context triple: [Juz 16, isEqualDivisionWith, other 29 ajza of the Quran]
-
A.
isDividedBy
Indicates that one quantity or entity serves as the divisor that evenly or proportionally separates another quantity or entity into parts.
-
B.
dividedBy
chosen
Indicates that one quantity is separated into a specified number of equal parts or groups by another quantity, representing a division relationship between them.
-
C.
isDivisible
Indicates that one quantity can be evenly divided by another without leaving a remainder.
-
D.
usesDivisor
Indicates that one entity employs another entity as a divisor in a division or modular arithmetic operation.
-
E.
divisionResultOf
Indicates that one quantity is the numerical result obtained by dividing another quantity by a specified divisor.
- 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_69ca828d13088190b222be7aa9f9315c |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a40a0508190864479c2c41b12cb |
completed | March 31, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69cae92d94448190b4425bbfb64c658c |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:02 p.m.