Triple

T12386015
Position Surface form Disambiguated ID Type / Status
Subject Matthew Holworthy E295865 entity
Predicate hasFamilyName P18 FINISHED
Object Holworthy E195258 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: Holworthy | Statement: [Matthew Holworthy, hasFamilyName, Holworthy]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Holworthy
Context triple: [Matthew Holworthy, hasFamilyName, Holworthy]
  • A. Holworthy chosen
    Holworthy is a surname most notably associated with Sir Matthew Holworthy, a historical English figure and benefactor.
  • B. Banwell
    Banwell is a village and civil parish in North Somerset, England, known for its historic caves and medieval architecture.
  • C. Warminster
    Warminster is a market town in Wiltshire, England, known for its historic architecture, surrounding countryside, and role as a local transport and service hub.
  • D. Westwick
    Westwick is a small village in Cambridgeshire, England, situated just northwest of Cambridge and closely linked administratively and geographically with the nearby village of Oakington.
  • E. Holwell
    Holwell is a small rural village located within the North Hertfordshire district of Hertfordshire, England.
  • 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_69d6ad9e653c8190b1473c860ee53dae completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d93fbd489c819098233a111442762e completed April 10, 2026, 6:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69f62ac939bc819081629b9eef20c4e7 completed May 2, 2026, 4:48 p.m.
Created at: April 8, 2026, 9:54 p.m.