Triple

T5365981
Position Surface form Disambiguated ID Type / Status
Subject Lord Goring E103131 entity
Predicate familyName P18 FINISHED
Object Goring E467100 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: Goring | Statement: [Lord Goring, familyName, Goring]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Goring
Context triple: [Lord Goring, familyName, Goring]
  • A. Goring chosen
    Goring is an English surname historically associated with the aristocratic Goring family, including figures such as Charles, Lord Goring.
  • B. Goring-on-Thames
    Goring-on-Thames is a picturesque village on the River Thames in South Oxfordshire, England, known for its historic architecture and scenic countryside setting.
  • C. Burgess Hill
    Burgess Hill is a town in southeastern England known as a commuter hub with residential areas and light industry, situated within the county of West Sussex.
  • D. Adcote
    Adcote is a Victorian country house in Shropshire, England, designed in the late 19th century by architect Richard Norman Shaw in a distinctive Tudor Revival style.
  • E. Northbourne
    Northbourne is a small village and civil parish in Kent, England, known for its rural character and historic church.
  • 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_69bd43daa3e4819090b59d127db70e57 completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd8682d18c8190bbb35cc75c8a7c12 completed March 20, 2026, 5:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69bf334553148190a5c53bda473c17c3 completed March 22, 2026, 12:09 a.m.
Created at: March 20, 2026, 2:02 p.m.