Triple
T13604685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | People of the Ditch |
E325030
|
entity |
| Predicate | mentionedInVerses |
P66106
|
FINISHED |
| Object | Qur'an 85:4-8 |
—
|
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: Qur'an 85:4-8 | Statement: [People of the Ditch, mentionedInVerses, Qur'an 85:4-8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mentionedInVerses Context triple: [People of the Ditch, mentionedInVerses, Qur'an 85:4-8]
-
A.
notedInRevelationFor
chosen
Indicates that something is mentioned, highlighted, or recorded within a revelation specifically in reference to a particular entity.
-
B.
mentionedInInscription
Indicates that an entity is referenced or named within a specific inscription or inscribed text.
-
C.
mentionedWith
Indicates that two entities are mentioned together or in close association within the same context, such as a document, sentence, or conversation.
-
D.
containsVerse
Indicates that one entity (typically a text or collection) includes a specific verse as part of its content.
-
E.
mentionedAs
Indicates that one entity is referred to or cited by name or description in the context of 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_69d80769eaf081909d82f44e484d6113 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbbb9ee3f081909056dc1a92c40b7a |
completed | April 12, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69dbae1b3ee481909bd43ded6227a3e5 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:50 p.m.