Triple

T11023311
Position Surface form Disambiguated ID Type / Status
Subject Kenneth Lawford E260548 entity
Predicate hasSurname P18 FINISHED
Object Lawford E48362 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: Lawford | Statement: [Kenneth Lawford, hasSurname, Lawford]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lawford
Context triple: [Kenneth Lawford, hasSurname, Lawford]
  • A. Lawford chosen
    Lawford is an English-origin surname most notably associated with actor Peter Lawford and, by marriage, the Kennedy political family.
  • B. Lawford
    Lawford is a village in Essex, England, situated within the scenic Dedham Vale Area of Outstanding Natural Beauty.
  • C. Marford
    Marford is a village in Wrexham County Borough, Wales, known for its distinctive Gothic-style architecture and historic character.
  • D. Radford
    Radford is a masculine given name of English origin that has been used both as a first name and surname.
  • E. Ashford
    Ashford is a small rural town in northern New South Wales, Australia, known for agriculture and its proximity to natural attractions such as caves and rivers.
  • 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_69d6aa9687448190b28d353b1b6a610e completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d797be9f148190a3a967bad5947496 completed April 9, 2026, 12:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69e3a997d7bc8190982467039e0f5504 completed April 18, 2026, 3:56 p.m.
Created at: April 8, 2026, 9:25 p.m.