Triple
T35785300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sassoon |
E1034548
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Middle Eastern surname |
C13336
|
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: Middle Eastern surname Context triple: [Sassoon, instanceOf, Middle Eastern surname]
-
A.
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.
-
B.
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).
-
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.
Persian-language surname
A Persian-language surname is a family name originating from the Persian language and cultural tradition, often reflecting ancestry, geography, occupation, or personal attributes.
-
E.
Hebrew-language surname
chosen
A Hebrew-language surname is a family name derived from or adapted into the Hebrew language, often reflecting Hebrew words, biblical names, places, or cultural-historical origins within Jewish 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_69f76e1575908190aaa306d843b41c14 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.