Triple
T25095240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tadaksahak |
E628569
|
entity |
| Predicate | usesScriptForReligion |
P56479
|
FINISHED |
| Object | Arabic script |
—
|
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 script | Statement: [Tadaksahak, usesScriptForReligion, Arabic script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesScriptForReligion Context triple: [Tadaksahak, usesScriptForReligion, Arabic script]
-
A.
isUsedByReligion
chosen
Indicates that something (such as an object, practice, text, or symbol) is employed or utilized within the context of a particular religion.
-
B.
usedReligionFor
Indicates that an entity employed religion as a means or tool to achieve some purpose, goal, or effect.
-
C.
hasReligious
Indicates that an entity is associated with, practices, or adheres to a particular religion or religious affiliation.
-
D.
scripturalUse
Indicates that one entity is used as a scriptural reference, source, or basis within the context or content of another entity.
-
E.
primaryScriptureOfReligion
Indicates that a given text serves as the main or authoritative scripture for a particular religion.
- 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_69e2ff2f58e881908340527bc5d34f07 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 18, 2026, 6:24 a.m.