Triple
T35359049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edward Hurwitz |
E1021420
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | given name holder of Hurwitz surname |
C45580
|
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: given name holder of Hurwitz surname Context triple: [Edward Hurwitz, instanceOf, given name holder of Hurwitz surname]
-
A.
given name and surname combination bearer
chosen
A given name and surname combination bearer is an individual who holds and is identified by a specific pairing of a first (given) name and last (family) name.
-
B.
person with Dutch surname
A person with Dutch surname is an individual whose family name originates from the Dutch language and cultural or geographic heritage of the Netherlands.
-
C.
Polish given name and surname combination
A Polish given name and surname combination represents a full personal name constructed according to Polish linguistic, cultural, and naming conventions.
-
D.
given-name-and-surname-ambiguous-person
A given-name-and-surname-ambiguous-person is an individual whose name structure makes it unclear which component is the given name and which is the surname, often due to cultural, linguistic, or formatting variations.
-
E.
Hungarian-language surname–given name combination
A Hungarian-language surname–given name combination is a personal name structure in which the family name precedes the given name, following Hungarian naming conventions and orthographic rules.
- 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_69f76def44c881908a20e8008572eb44 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:03 p.m.