Triple
T34378804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ibn Ahmad |
E882368
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Arabic-language name element |
C39678
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Arabic-language name element Context triple: [ibn Ahmad, instanceOf, Arabic-language name element]
-
A.
Arabic given name
An Arabic given name is a personal name of Arabic linguistic and cultural origin, often derived from religious, historical, or meaningful lexical roots and typically used as a first name in Arabic-speaking and Islamic societies.
-
B.
Arabic-language surname
An Arabic-language surname is a family name derived from Arabic linguistic, cultural, or geographic origins, often reflecting ancestry, profession, place, or tribal affiliation.
-
C.
Arabic patronymic name
chosen
An Arabic patronymic name is a personal name component that identifies an individual as the child or descendant of a specific ancestor, typically using connectors like "ibn/bin" (son of) or "bint" (daughter of).
-
D.
Arabic nisba
An Arabic nisba is a relational adjective, typically formed by adding a suffix like -ī or -iyya to a noun, that indicates origin, affiliation, or connection to a place, tribe, group, or concept.
-
E.
Arabic term
An Arabic term is a word or phrase originating from the Arabic language that conveys a specific concept, object, action, or expression within Arabic linguistic and cultural contexts.
- F. None of above.
Provenance (1 batch)
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_69f349bf5d7481908dd5da4cbdf74047 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:59 a.m.