Triple
T25848721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abdul Khalek Hassouna |
E651140
|
entity |
| Predicate | hasArabicNameComponent |
P73712
|
FINISHED |
| Object | Abdul |
—
|
NE NERFINISHED |
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: Abdul | Statement: [Abdul Khalek Hassouna, hasArabicNameComponent, Abdul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArabicNameComponent Context triple: [Abdul Khalek Hassouna, hasArabicNameComponent, Abdul]
-
A.
hasNameInArabic
Indicates that an entity is associated with a specific name expressed in the Arabic language.
-
B.
hasGivenNameFormInArabic
chosen
Indicates that an entity has a specific given-name form expressed in the Arabic language.
-
C.
hasLadinName
Indicates that an entity is associated with a specific name expressed in the Ladin language.
-
D.
hasKeyTermArabic
Indicates that an entity is associated with a specific key term expressed in the Arabic language.
-
E.
hasPersianName
Indicates that an entity is associated with a name expressed in the Persian language.
- 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_69e7ab39035c8190be15c8aaee1bb858 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 22, 2026, 7:57 a.m.