Triple

T3006150
Position Surface form Disambiguated ID Type / Status
Subject Williams E81905 entity
Predicate hasVariantForm P457 FINISHED
Object Williamson E32984 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: Williamson | Statement: [Williams, hasVariantForm, Williamson]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Williamson
Context triple: [Williams, hasVariantForm, Williamson]
  • A. Williamson chosen
    Williamson is a surname of English and Scottish origin, traditionally meaning "son of William."
  • B. Hardin
    Hardin is the surname of Lil Hardin Armstrong, a pioneering jazz pianist, composer, and bandleader who was a key figure in early jazz and Louis Armstrong’s second wife.
  • C. Brewster
    Brewster is an English occupational surname historically associated with brewing ale or beer.
  • D. Brewster
    Brewster is a coastal town on Cape Cod in Massachusetts known for its scenic beaches, historic charm, and bayside conservation lands.
  • E. Brewster
    Brewster is the given name of Brewster Kahle, an American computer engineer and digital librarian best known as the founder of the Internet Archive.
  • 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_69ad8b1c4de88190a83b7cefaa1f2842 completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69ad9a48f0888190bdec150dac623851 completed March 8, 2026, 3:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69b12e5b35e48190a9319a545d041ccc completed March 11, 2026, 8:56 a.m.
Created at: March 8, 2026, 3 p.m.