Triple

T9948180
Position Surface form Disambiguated ID Type / Status
Subject Sir Matthew Holworthy E195258 entity
Predicate hasSurname 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: [Sir Matthew Holworthy, hasSurname, Holworthy]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Holworthy
Context triple: [Sir Matthew Holworthy, hasSurname, 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_69ca82e96a108190932bd1fc4acd73a0 completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cdb659307c81908279adb641ceef86 completed April 2, 2026, 12:20 a.m.
NED1 Entity disambiguation (via context triple) batch_69d2292b50a881909ff868487639fbfd completed April 5, 2026, 9:19 a.m.
Created at: March 30, 2026, 8:45 p.m.