Triple
T14843793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Earthquake |
E349031
|
entity |
| Predicate | scripturalNumbering |
P88933
|
FINISHED |
| Object | Surah 99 |
—
|
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: Surah 99 | Statement: [The Earthquake, scripturalNumbering, Surah 99]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scripturalNumbering Context triple: [The Earthquake, scripturalNumbering, Surah 99]
-
A.
scripturalNumberingSystem
chosen
Indicates a relationship where a particular numbering system is used to organize, reference, or index passages within a scriptural text.
-
B.
numberingInSeptuagintVulgate
Indicates that the entity uses the chapter or verse numbering system as found in the Septuagint and Vulgate traditions.
-
C.
canonicalNumberingInMostEnglishBibles
Indicates that the entity is ordered or numbered according to the standard canonical sequence used in most English-language Bibles.
-
D.
numberInBiblicalText
Indicates that a specific number appears within, or is referenced by, a given passage or unit of biblical text.
-
E.
usesVerseNumbers
Indicates that one entity organizes or references content using verse numbers associated with another 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_69d822ec69008190a9232caa68836872 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded291103c8190a64cfe700bfee197 |
completed | April 14, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69de8c13418c819088ff9905ace1416a |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:53 a.m.