Triple

T11600207
Position Surface form Disambiguated ID Type / Status
Subject A130 E275107 entity
Predicate connectsTown P845 FINISHED
Object Great Dunmow E164176 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: Great Dunmow | Statement: [A130, connectsTown, Great Dunmow]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Great Dunmow
Context triple: [A130, connectsTown, Great Dunmow]
  • A. Dunmow chosen
    Dunmow is a historic market town in Essex, England, known for its medieval roots and the traditional "Flitch Trials" custom.
  • B. Great Horkesley
    Great Horkesley is a village in Essex, England, situated within the scenic Dedham Vale countryside near the Suffolk border.
  • C. Great Broughton
    Great Broughton is a village in Cumbria, England, known for its rural setting near the Lake District.
  • D. Great Shelford
    Great Shelford is a large, affluent commuter village and civil parish just south of Cambridge in eastern England, known for its strong community amenities and proximity to the city.
  • E. Great Staughton
    Great Staughton is a rural village and civil parish in Cambridgeshire, England, known for its historic church and traditional English countryside setting.
  • 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_69d6aae6b14c81908dc5a74bad7591f9 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8954c3c248190bcccd4c7ff667b3a completed April 10, 2026, 6:14 a.m.
NED1 Entity disambiguation (via context triple) batch_69e8a7f018a881908f4b206699044ceb completed April 22, 2026, 10:50 a.m.
Created at: April 8, 2026, 9:38 p.m.