Triple

T21814890
Position Surface form Disambiguated ID Type / Status
Subject John Goodricke E538579 entity
Predicate familyName P18 FINISHED
Object Goodricke NE NERFINISHED

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: Goodricke | Statement: [John Goodricke, familyName, Goodricke]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Goodricke
Context triple: [John Goodricke, familyName, Goodricke]
  • A. Goodricke chosen
    Goodricke is a surname of English origin, historically borne by several notable figures including astronomer John Goodricke.
  • B. Enderby
    Enderby is a village and civil parish in Leicestershire, England, situated near Leicester and known historically for its involvement in the hosiery and footwear industries.
  • C. Enderby
    Enderby is a small city in the North Okanagan region of British Columbia, Canada, known for its rural charm and proximity to the Shuswap River.
  • D. Baron Howe
    Baron Howe is a British noble title historically associated with the distinguished naval commander Admiral Richard Howe.
  • E. Paulet
    Paulet is a surname most notably associated with Pedro Paulet, a pioneering Peruvian engineer and early rocket propulsion visionary.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0c473f0f8819086c9d1b4a143bd67 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f07cc99bbc8190bf074930f361af7d completed April 28, 2026, 9:24 a.m.
Created at: April 16, 2026, 6:54 p.m.