Triple
T26062158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salah |
E657287
|
entity |
| Predicate | secondaryScripturalSource |
P175198
|
FINISHED |
| Object | Hadith |
—
|
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: Hadith | Statement: [Salah, secondaryScripturalSource, Hadith]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryScripturalSource Context triple: [Salah, secondaryScripturalSource, Hadith]
-
A.
scripturalSourceType
Indicates the type or category of source from which a scriptural text or reference is derived.
-
B.
scriptureContributedTo
Indicates that an entity played a role in creating, authoring, or otherwise contributing content to a particular scripture or sacred text.
-
C.
scriptureType
Indicates the classification or category of a scripture in relation to its type or genre.
-
D.
receivedScripture
Indicates that one entity has been given or accepted a body of sacred or authoritative religious writings from another source.
-
E.
oneOfPrimaryScripturesAlongWith
Indicates that one entity is among the primary scriptures considered together with another entity (or set of entities) as part of a core scriptural group.
- 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_69ee5bbd788481909e22bd7153d0c037 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6cee547108190ad3bc84297d8f516 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6cee3604c81908a07eade2f39064e |
completed | May 3, 2026, 4:28 a.m. |
Created at: April 26, 2026, 7:18 p.m.