Triple
T34157375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Scudder (missionary, 19th century, disambiguation) |
E876174
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | name disambiguation |
C9328
|
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: name disambiguation Context triple: [John Scudder (missionary, 19th century, disambiguation), instanceOf, name disambiguation]
-
A.
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.
-
B.
disambiguation of multiple people with surname Bell
chosen
A disambiguation of multiple people with surname Bell is a reference construct that distinguishes and organizes different individuals sharing the Bell surname by their unique identifying attributes, such as given name, profession, and notable achievements.
-
C.
name
A name is a linguistic label or designation used to identify, distinguish, or refer to a specific entity, such as a person, place, object, or concept.
-
D.
namesake
A namesake is a person, place, or thing that shares the same name as, or is named after, another person, place, or thing.
-
E.
named entity
A named entity is a real-world object or concept that can be uniquely identified by a proper name, such as a person, organization, location, or product.
- 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_69f349ac987481908a8e6053f665bc8b |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:54 a.m.