Triple
T25659481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shia Imams |
E643336
|
entity |
| Predicate | haveLanguageOfScripture |
P1187
|
FINISHED |
| Object | Arabic |
—
|
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: Arabic | Statement: [Shia Imams, haveLanguageOfScripture, Arabic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveLanguageOfScripture Context triple: [Shia Imams, haveLanguageOfScripture, Arabic]
-
A.
hasLanguageOfScripture
chosen
Indicates that an entity’s scriptural or sacred texts are written or expressed in a specified language.
-
B.
hasScripture
Indicates that one entity possesses, is associated with, or is defined by a particular scripture or set of scriptural texts.
-
C.
hasClericalLanguage
Indicates that something is expressed using formal, religious, or church-related language or terminology.
-
D.
languageOfScripturalTradition
Indicates the language in which a given scriptural or religious textual tradition is expressed or transmitted.
-
E.
recognizesScripturesFrom
Indicates that one entity acknowledges or accepts certain scriptures as authoritative or valid based on another entity as their source or origin.
- 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_69e77e7e45648190a068ed3faa8016ea |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5faee68408190b602dc71ec5b83aa |
completed | May 2, 2026, 1:23 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 6:50 p.m.