Triple
T6517401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Cow |
E148299
|
entity |
| Predicate | containsAyatAlKursi |
P71348
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [The Cow, containsAyatAlKursi, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsAyatAlKursi Context triple: [The Cow, containsAyatAlKursi, true]
-
A.
containsMakkiVerses
Indicates that something (typically a chapter or section of a text) includes one or more verses that are classified as Makki (revealed in Mecca).
-
B.
containsBasmalah
Indicates that something (such as a text, document, or verse) includes the Basmalah phrase ("In the name of God, the Most Gracious, the Most Merciful") within it.
-
C.
quranicSurahMention
Indicates that a specific Quranic surah is mentioned, referenced, or cited in relation to another entity or context.
-
D.
commandInSurah
Indicates that a particular command or directive appears within a specified surah (chapter) of the Quran.
-
E.
isMeccanSurah
Indicates that a given surah (chapter of the Qur’an) was revealed in Mecca (i.e., is classified as a Meccan surah) rather than in Medina.
- 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_69c687e68e748190baceb9298f32d3ed |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ac0ece2081909c14accef90efd7c |
completed | March 27, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69c68ab98c78819081743e614df04e1d |
completed | March 27, 2026, 1:48 p.m. |
| PDg | Predicate description generation | batch_69c69f362ee4819090e8fa48caef7d7d |
completed | March 27, 2026, 3:16 p.m. |
Created at: March 27, 2026, 1:44 p.m.