Triple

T15993261
Position Surface form Disambiguated ID Type / Status
Subject Clothall E387891 entity
Predicate locatedNear P294 FINISHED
Object Baldock E211875 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: Baldock | Statement: [Clothall, locatedNear, Baldock]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Baldock
Context triple: [Clothall, locatedNear, Baldock]
  • A. Baldock chosen
    Baldock is a historic market town in the county of Hertfordshire, England.
  • B. Sawbridgeworth
    Sawbridgeworth is a historic market town in Hertfordshire, England, situated near the River Stort and known for its commuter links to London and surrounding countryside.
  • C. Berkhamsted
    Berkhamsted is a historic market town in Hertfordshire, England, known for its medieval castle remains and role as a commuter hub northwest of London.
  • D. Buckland
    Buckland is a small Inupiat community and city in northwestern Alaska situated along the Buckland River.
  • E. Buckland
    Buckland is a settled region of the Shire in J.R.R. Tolkien’s Middle-earth, lying east of the Brandywine River and known as the homeland of the Brandybuck family.
  • 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_69d86daa562c81908aacc179c0fe8fb5 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e15785347081908831b4cbc9a2dd45 completed April 16, 2026, 9:41 p.m.
NED1 Entity disambiguation (via context triple) batch_69ffdbc8a8a081908ac1b431f524d650 completed May 10, 2026, 1:13 a.m.
Created at: April 10, 2026, 4:54 a.m.