Triple

T10623064
Position Surface form Disambiguated ID Type / Status
Subject Scudder E250252 entity
Predicate hasNotableBearer P458 FINISHED
Object John Anderson Scudder E876174 NE FINISHED

How this triple was built (2 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: John Anderson Scudder | Statement: [Scudder, hasNotableBearer, John Anderson Scudder]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: John Anderson Scudder
Context triple: [Scudder, hasNotableBearer, John Anderson Scudder]
  • A. George Scudder
    George Scudder is an individual notable enough to be recognized as a bearer of the surname Scudder, though specific widely known public details about him are limited.
  • B. John Scudder chosen
    John Scudder is a name shared by several notable American figures, including physicians and missionaries active in the 18th and 19th centuries.
  • C. William Scudder
    William Scudder is a person notable enough to be specifically recorded as a bearer of the surname Scudder.
  • D. David Coit Scudder
    David Coit Scudder was a 19th-century American missionary known for his religious and educational work in India before his early death.
  • E. Thomas Scudder
    Thomas Scudder is a relatively obscure individual whose name is notably recorded as a bearer of the Scudder surname.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 batches)

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_69d6aa5993448190a493b790b8f85010 completed April 8, 2026, 7:19 p.m.
NER Named-entity recognition batch_69d6df7f11fc8190aed858f2e1443c08 completed April 8, 2026, 11:06 p.m.
NED1 Entity disambiguation (via context triple) batch_69e5e877c6188190817fb30f2c9a07bf completed April 20, 2026, 8:48 a.m.
Created at: April 8, 2026, 8:51 p.m.