Triple
T2873763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surah Al-Qalam |
E56825
|
entity |
| Predicate | hasRhymeStyle |
P43458
|
FINISHED |
| Object | early Meccan style |
—
|
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: early Meccan style | Statement: [Surah Al-Qalam, hasRhymeStyle, early Meccan style]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRhymeStyle Context triple: [Surah Al-Qalam, hasRhymeStyle, early Meccan style]
-
A.
hasTraditionalRhyme
Indicates that something is associated with or characterized by a conventional or culturally established rhyme.
-
B.
rhymeScheme
Indicates the pattern of end sounds in a sequence of lines, showing which lines rhyme with each other.
-
C.
hasLyricalStyle
Indicates that one entity possesses or is characterized by a particular lyrical style in relation to another entity or context.
-
D.
hasRhythmicStyle
Indicates that one entity exhibits or is characterized by a particular rhythmic pattern or style in its expression or behavior.
-
E.
hasStressPattern
Indicates that an entity (such as a word or phrase) follows a particular arrangement of stressed and unstressed units (e.g., syllables) in its pronunciation.
- F. None of above. chosen
Provenance (4 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_69ab4a4ced288190ab6d3e062d10f7f6 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abe0032ddc8190bb4d15ec7e3c63e8 |
completed | March 7, 2026, 8:21 a.m. |
| PD | Predicate disambiguation | batch_69abdd142e4c8190b424cb0c5ff40d04 |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abde2cdcc48190827195d3ae70aa19 |
completed | March 7, 2026, 8:13 a.m. |
Created at: March 6, 2026, 10:03 p.m.