Triple
T12428936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | النَّازِعَات |
E296971
|
entity |
| Predicate | تقرر |
P2704
|
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.
decides
Indicates that an entity makes a choice or determination between options, often resolving uncertainty or selecting a course of action.
-
B.
determined
chosen
Indicates that an entity has firmly decided on a course of action or conclusion, typically after consideration or effort.
-
C.
decidedIn
Indicates that a decision, ruling, or outcome was made within a particular case, proceeding, or deliberative context.
-
D.
wasDecidedBy
Indicates that a decision or outcome was determined or resolved by a specific agent or authority.
-
E.
decisionImplementedBy
Indicates that a particular decision is carried out, executed, or put into effect by a specified agent or 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_69d6ada0640c81908c061d7fb3d47786 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94df948308190ace333230a4a3b38 |
completed | April 10, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69d94d391c548190996a8c698357f273 |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:55 p.m.