Triple

T22653665
Position Surface form Disambiguated ID Type / Status
Subject J. R. Ackerley E559161 entity
Predicate familyName P18 FINISHED
Object Ackerley 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: Ackerley | Statement: [J. R. Ackerley, familyName, Ackerley]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ackerley
Context triple: [J. R. Ackerley, familyName, Ackerley]
  • A. Ackerley chosen
    Ackerley is an English surname most notably associated with the writer and editor J. R. Ackerley.
  • B. Rackerby
    Rackerby is a small unincorporated rural community in Northern California known for its forested surroundings and quiet, sparsely populated setting.
  • C. Arfield
    Arfield is the surname of Scott Arfield, a professional footballer known for playing as a midfielder for clubs such as Burnley and Rangers and representing the Canadian national team.
  • D. Homersfield
    Homersfield is a small village and civil parish on the River Waveney in eastern England, known for its historic bridge and rural Suffolk setting.
  • E. Bakerville
    Bakerville is a small village within the town of New Hartford in Litchfield County, Connecticut.
  • 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_69e245489dd88190b1f674acf61c8769 completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f17659e4dc81909cf6943c1c986ef9 completed April 29, 2026, 3:09 a.m.
Created at: April 17, 2026, 3:06 p.m.