Triple
T21574106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | الإنسان الكامل |
E532353
|
entity |
| Predicate | يُربطبـ |
P144317
|
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.
rehabilitates
Indicates that one entity restores, reforms, or helps another entity return to a previous or improved functional, social, or legal state after damage, illness, or wrongdoing.
-
B.
مرتبطب
Indicates a relationship of being connected, associated, or related to something or someone.
-
C.
remedy
Indicates that one entity serves to cure, alleviate, or counteract a problem, illness, or undesirable condition affecting another entity.
-
D.
rehabilitatedBy
Indicates that an entity has been restored, treated, or brought back to a better or functional state through the actions or intervention of another entity.
-
E.
treats
Indicates that one entity provides medical care or therapeutic intervention to another entity.
- F. None of above. chosen
Provenance (4 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_69e0c4618bec8190bcb0feb74568cbb1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eee9cef2748190990a81967d49b706 |
completed | April 27, 2026, 4:45 a.m. |
| PD | Predicate disambiguation | batch_69e6320c8c2c81908bf031447d66a052 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e633bf34c481909925d8dc1a633a65 |
completed | April 20, 2026, 2:10 p.m. |
Created at: April 16, 2026, 6:30 p.m.