Triple

T7149366
Position Surface form Disambiguated ID Type / Status
Subject Steve Alford E166651 entity
Predicate hasSurname P18 FINISHED
Object Alford E166651 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: Alford | Statement: [Steve Alford, hasSurname, Alford]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Alford
Context triple: [Steve Alford, hasSurname, Alford]
  • A. Alford chosen
    Alford is a surname of English origin borne by various notable individuals, including American basketball coach and former player Steve Alford.
  • B. Alford
    Alford is a small market town in the East Lindsey district of Lincolnshire, England, known for its historic buildings and rural character.
  • C. Alford
    Alford is a small rural town in western Massachusetts known for its scenic landscapes and quiet, residential character.
  • D. Forsythe
    Forsythe is a surname most prominently associated with American choreographer William Forsythe, renowned for his innovative contributions to contemporary ballet.
  • E. Oakey
    Oakey is a rural town in Queensland, Australia, situated on the Darling Downs west of Toowoomba.
  • 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_69c68886779c8190a8e3fbabffe68253 completed March 27, 2026, 1:39 p.m.
NER Named-entity recognition batch_69c6e7f130e08190bc5ca99f90f9de92 completed March 27, 2026, 8:26 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7ada940e08190b16e97e363801e75 completed March 28, 2026, 10:30 a.m.
Created at: March 27, 2026, 2:46 p.m.