Triple
T36427548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juz 26 |
E897343
|
entity |
| Predicate | beginsAtSurahNumber |
P134268
|
FINISHED |
| Object | 46 |
—
|
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: 46 | Statement: [Juz 26, beginsAtSurahNumber, 46]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beginsAtSurahNumber Context triple: [Juz 26, beginsAtSurahNumber, 46]
-
A.
beginsAtChapter
chosen
Indicates that an entity (such as a section, event, or reference) starts or first occurs at a specified chapter in a structured work.
-
B.
commandInSurah
Indicates that a particular command or directive appears within a specified surah (chapter) of the Quran.
-
C.
omittedAtStartOfSurah
Indicates that something (such as a phrase, verse, or formula) is left out or not present at the beginning of a surah.
-
D.
beginsWithInQuran
Indicates that one textual element starts with another specific sequence of characters as it appears at the beginning of a verse or passage in the Quran.
-
E.
quranSurahNumber
Indicates the numerical position or identifier assigned to a specific surah (chapter) within the Quran.
- 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_69f76e559b10819099d6655a6e14587c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:10 p.m.