Triple
T27172579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mughniyeh |
E682958
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Lebanese family name |
C6169
|
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: Lebanese family name Context triple: [Mughniyeh, instanceOf, Lebanese family name]
-
A.
Arabic patronymic name
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).
-
B.
Arabic-language surname
chosen
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.
Armenian surname
An Armenian surname is a family name of Armenian origin, often characterized by distinctive suffixes such as "-yan" or "-ian," that reflects ancestral lineage, geographic roots, or occupational heritage within Armenian culture.
-
D.
Hebrew patronymic name
A Hebrew patronymic name is a personal name that identifies an individual as the child of a specific father, typically formed with the prefix "ben" (son of) or "bat" (daughter of) followed by the father's given name.
-
E.
Lebanese-American person
A Lebanese-American person is an individual of Lebanese heritage who lives in, is a citizen of, or strongly identifies with both Lebanese and American cultures, histories, and communities.
- 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_69eefad086808190ab89816c0c300476 |
completed | April 27, 2026, 5:57 a.m. |
Created at: April 27, 2026, 9:24 a.m.