Triple
T12751134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | People of the Garden |
E304731
|
entity |
| Predicate | mentionedInVerseRange |
P63729
|
FINISHED |
| Object | Qur'an 68:17-33 |
—
|
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 68:17-33 | Statement: [People of the Garden, mentionedInVerseRange, Qur'an 68:17-33]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mentionedInVerseRange Context triple: [People of the Garden, mentionedInVerseRange, Qur'an 68:17-33]
-
A.
hasVerseRange
Indicates a relationship where a text or passage is associated with a specific contiguous range of verses it spans.
-
B.
containsVerse
Indicates that one entity (typically a text or collection) includes a specific verse as part of its content.
-
C.
mentionedWith
chosen
Indicates that two entities are mentioned together or in close association within the same context, such as a document, sentence, or conversation.
-
D.
mentionedAs
Indicates that one entity is referred to or cited by name or description in the context of another entity.
-
E.
hasVersesIn
Indicates that one entity (typically a text, chapter, or section) contains or is composed of verses found within another entity (such as a book, collection, or scripture).
- 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_69d7bdf1fcd081909ffb0e0d6fa3a07d |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96406e97c8190b79081039847115c |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:27 p.m.