Triple
T36001739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | العرش |
E1041149
|
entity |
| Predicate | يُستدل_به_في |
P41975
|
FINISHED |
| Object | إثبات كمال قدرة الله |
—
|
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: إثبات كمال قدرة الله | Statement: [العرش, يُستدل_به_في, إثبات كمال قدرة الله]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: يُستدل_به_في Context triple: [العرش, يُستدل_به_في, إثبات كمال قدرة الله]
-
A.
usedAsExampleIn
chosen
Indicates that one entity is cited or presented as an illustrative example within another entity, such as a text, discussion, or explanation.
-
B.
areUsedIn
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
C.
arisesIn
Indicates that something originates, emerges, or comes into existence within a specified context, source, or location.
-
D.
usedInResult
Indicates that something (such as a resource, method, or input) is utilized or incorporated in producing a particular result or outcome.
-
E.
existsBecauseOf
Indicates that one entity’s existence is caused, enabled, or brought about by another entity.
- 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_69f76e2a02208190aedd1f9025a8b300 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7acaec1508190a38f2ac9cc5383e7 |
completed | May 3, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f7ab75387c819091afc3c2128eb903 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.