Triple
T23318399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abd al-Jawad |
E590776
|
entity |
| Predicate | hasComponent |
P35
|
FINISHED |
| Object | Abd |
—
|
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: Abd | Statement: [Abd al-Jawad, hasComponent, Abd]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Abd Context triple: [Abd al-Jawad, hasComponent, Abd]
-
A.
ʿAbd
chosen
ʿAbd is an Arabic name element meaning “servant (of),” commonly used as the first part of theophoric names such as ʿAbd al-Raḥmān.
-
B.
Abdi
Abdi is a masculine given name of Arabic origin commonly used in various Muslim-majority cultures.
-
C.
Abas
Abas is a figure in Greek mythology known primarily as the son of Hypermnestra and a king of Argos in some traditions.
-
D.
Abdel-
Abdel- is a common Arabic name prefix, derived from “ʿAbd al-,” meaning “servant of the,” typically used in theophoric names such as Abdel-Rahman or Abdel-Karim.
-
E.
Abdul
Abdul is a common male given name of Arabic origin meaning "servant of" (typically followed by one of the names of God).
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e25d1d32188190948eb76909d1dcc3 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1978372948190bad066893c4e0768 |
completed | April 29, 2026, 5:30 a.m. |
Created at: April 17, 2026, 5:07 p.m.