Triple
T19333226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lak |
E483549
|
entity |
| Predicate | usesLanguageInReligion |
P69775
|
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: [Lak, usesLanguageInReligion, Arabic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesLanguageInReligion Context triple: [Lak, usesLanguageInReligion, Arabic]
-
A.
usedForReligiousLanguage
Indicates that something is employed specifically in the context of religious language, such as for expressing, communicating, or performing religious beliefs, practices, or rituals.
-
B.
positionOnReligiousLanguage
Indicates a stance or viewpoint someone holds regarding how religious language should be understood, interpreted, or used.
-
C.
isUsedByReligion
Indicates that something (such as an object, practice, text, or symbol) is employed or utilized within the context of a particular religion.
-
D.
languageOfReligiousLife
chosen
Indicates the language primarily used in the religious practices, rituals, or spiritual life associated with an entity.
-
E.
hasLanguageOfScripture
Indicates that an entity’s scriptural or sacred texts are written or expressed in a specified language.
- 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_69d8e8d13e3c81909d91d1d5ec37c095 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e61642f49c81909226cfd701f7c139 |
completed | April 20, 2026, 12:04 p.m. |
| PD | Predicate disambiguation | batch_69e4dd12303c8190a2027c062b2dff40 |
completed | April 19, 2026, 1:48 p.m. |
Created at: April 10, 2026, 1:33 p.m.