Triple
T14550194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Clot |
E341394
|
entity |
| Predicate | hasVerseRangeForFirstRevelation |
P46989
|
FINISHED |
| Object | verses 1–5 |
—
|
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: verses 1–5 | Statement: [The Clot, hasVerseRangeForFirstRevelation, verses 1–5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVerseRangeForFirstRevelation Context triple: [The Clot, hasVerseRangeForFirstRevelation, verses 1–5]
-
A.
hasVerseRange
Indicates a relationship where a text or passage is associated with a specific contiguous range of verses it spans.
-
B.
firstRevealedVerses
chosen
Indicates that the related verses are the initial ones revealed or disclosed in a given religious or textual tradition.
-
C.
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).
-
D.
hasVersesBy
Indicates a relationship where a work, such as a song or poem, contains verses authored or written by a specific creator.
-
E.
hasRevelationPeriod
Indicates the time span or phase during which a revelation, disclosure, or unveiling of something occurs or is valid.
- 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_69d822db9c8481908213ceb39585f792 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb2ed2b4c8190945bd26531c71f1f |
completed | April 14, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69de5c546c7081909e27d504ec360c5c |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:23 a.m.