Triple
T15350950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | سورة تبت |
E367048
|
entity |
| Predicate | تتضمن حكماً عقدياً |
P93123
|
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.
involvedAgreement
Indicates that an entity participates in, is a party to, or is otherwise associated with a specific agreement or contract.
-
B.
containsJudgmentIn
chosen
Indicates that one entity includes or embeds a specific judgment or decision within it.
-
C.
legalStandardOftenIncludes
Indicates that a particular legal standard commonly or typically encompasses or contains another specified element, criterion, or requirement.
-
D.
contractValue
Indicates the monetary worth or agreed-upon financial amount specified in a contract between parties.
-
E.
allegedClause
Indicates that a clause or statement is claimed or asserted to be true, typically without confirmed proof or legal determination.
- 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_69d85a1355608190a6673ddb67231d54 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e290efc8190b22c95dcd3e5f57f |
completed | April 16, 2026, 1:40 a.m. |
| PD | Predicate disambiguation | batch_69deca991e5081908b0df3d1ee7d5338 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:17 a.m.