Triple
T11933453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Enshrouded One |
E283973
|
entity |
| Predicate | scripturalSourceLanguage |
P75413
|
FINISHED |
| Object | Classical 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: Classical Arabic | Statement: [The Enshrouded One, scripturalSourceLanguage, Classical Arabic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scripturalSourceLanguage Context triple: [The Enshrouded One, scripturalSourceLanguage, Classical Arabic]
-
A.
scripturalLanguageName
chosen
Indicates the name of the language in which a given scripture or sacred text is written.
-
B.
hasLanguageOfScripture
Indicates that an entity’s scriptural or sacred texts are written or expressed in a specified language.
-
C.
usedScriptureTranslation
Indicates that one entity employed or relied on a particular translation of scripture in its actions, works, or communications.
-
D.
scriptureTypeTranslated
Indicates that a scripture or sacred text has been translated into a particular type, version, or format.
-
E.
scriptureTranslatedBy
Indicates that a particular scripture has been translated by a specific agent (such as a person, group, or organization).
- 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_69d6ab2ce9c48190b5d39511b524f666 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d90305015c81908edb0d9d3d012b2e |
completed | April 10, 2026, 2:02 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3af0188190bfb22be5c97b3349 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.