Triple
T2296033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surah Al-Mujadila |
E51614
|
entity |
| Predicate | verseStructure |
P6967
|
FINISHED |
| Object | rhymed prose |
—
|
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: rhymed prose | Statement: [Surah Al-Mujadila, verseStructure, rhymed prose]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: verseStructure Context triple: [Surah Al-Mujadila, verseStructure, rhymed prose]
-
A.
poeticStructure
Indicates a relationship where one entity defines, embodies, or specifies the formal poetic organization (such as meter, rhyme scheme, or stanza pattern) used by another entity.
-
B.
textualStructure
Indicates how parts of a text are organized and related to each other within its overall structure.
-
C.
refrainStructure
Indicates a structural relationship where a recurring refrain section is organized, positioned, or patterned within a larger composition or sequence.
-
D.
grammaticalStructure
Indicates the way linguistic elements are organized and related within a sentence or phrase according to grammatical rules.
-
E.
verseForm
chosen
Indicates the specific structural or metrical pattern in which a verse or poem is composed.
- 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_69a88b0a9f248190bcff941463d8f65a |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abcd0e42248190ada33b84d75caa64 |
completed | March 7, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_69abc589295c819092989820c2b4e9d8 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:49 p.m.