Triple

T15028045
Position Surface form Disambiguated ID Type / Status
Subject William Oldham E378267 entity
Predicate name P16 FINISHED
Object William Oldham unclear NED1 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: William Oldham | Statement: [William Oldham, name, William Oldham]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: William Oldham
Context triple: [William Oldham, name, William Oldham]
  • A. William Oldham
    William Oldham was an American Revolutionary War officer after whom Oldham County, Kentucky, was named.
  • B. William Oldham
    William Oldham is an American singer-songwriter and actor best known for his influential indie folk and alt-country music released under the stage name Will Oldham or Bonnie "Prince" Billy.
  • C. William Cleland
    William Cleland was a Scottish Covenanter and soldier known for leading the Cameronian regiment in late 17th-century conflicts against Jacobite forces.
  • D. William Scudder
    William Scudder is a person notable enough to be specifically recorded as a bearer of the surname Scudder.
  • E. Thomas Parsons
    Thomas Parsons is a relatively obscure individual whose name is shared with multiple historical and contemporary figures across various fields.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide. chosen

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_69d85cd46b2c819090d054c27787f677 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69ded7e0e8c88190ac6f5786b4d4040f completed April 15, 2026, 12:12 a.m.
NED1 Entity disambiguation (via context triple) batch_69fe9dd967588190821cf47e9734db21 completed May 9, 2026, 2:37 a.m.
Created at: April 10, 2026, 2:58 a.m.