Triple
T25637165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles Boone (name) |
E642733
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | English-language masculine given name and surname combination |
C91
|
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: English-language masculine given name and surname combination Context triple: [Charles Boone (name), instanceOf, English-language masculine given name and surname combination]
-
A.
English-language given name
An English-language given name is a personal name used to identify an individual in English-speaking contexts, typically assigned at birth or during a naming ceremony and used in everyday address.
-
B.
English-language family name
An English-language family name is a hereditary surname originating from English-speaking cultures, often derived from occupations, locations, personal characteristics, or ancestral given names.
-
C.
English masculine given name
chosen
An English masculine given name is a personal first name traditionally used for boys and men in English-speaking cultures, often derived from historical, biblical, or linguistic roots specific to the English language.
-
D.
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.
-
E.
German-language given name and surname combination
A German-language given name and surname combination is a full personal name constructed from a first name and a family name that both originate from or are commonly used in German-speaking regions.
- 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 21, 2026, 5:34 p.m.