Triple
T21574118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | الإنسان الكامل |
E532353
|
entity |
| Predicate | يُميَّزبـ |
P128575
|
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.
distinguishingTrait
chosen
Indicates that a particular characteristic or feature uniquely differentiates one entity from another.
-
B.
characterizedBy
Indicates that one entity possesses a defining quality, feature, or attribute expressed by another entity.
-
C.
distinctiveMarking
Indicates that one entity bears a unique or distinguishing visual feature or pattern that sets it apart from others.
-
D.
introducesDistinction
Indicates that one entity establishes or makes clear a conceptual or categorical difference between two or more entities or ideas.
-
E.
distinction
Indicates that one entity is recognized, treated, or classified as different or separate from another.
- 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_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. |
Created at: April 16, 2026, 6:30 p.m.