Triple
T6344204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HoopoeBirdStory |
E142703
|
entity |
| Predicate | associatedWithVerseRange |
P27216
|
FINISHED |
| Object | Quran 27:20-28 |
—
|
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: Quran 27:20-28 | Statement: [HoopoeBirdStory, associatedWithVerseRange, Quran 27:20-28]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithVerseRange Context triple: [HoopoeBirdStory, associatedWithVerseRange, Quran 27:20-28]
-
A.
hasVerseRange
chosen
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.
hasVersesBy
Indicates a relationship where a work, such as a song or poem, contains verses authored or written by a specific creator.
-
D.
associatedBiblicalBook
Indicates that one entity is linked or connected to a specific book of the Bible as its relevant or referenced scriptural source.
-
E.
featuresAdditionalVersesBy
Indicates that a work includes extra or bonus verses contributed by another creator beyond the primary one.
- 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_69c008d5ab108190b346c465696824a9 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0674702d08190806ef0998960b797 |
completed | March 22, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69c060ea1a988190889e47b7e0c819b8 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:31 p.m.