Triple

T3089680
Position Surface form Disambiguated ID Type / Status
Subject Suffolk E64456 entity
Predicate containsSettlement P847 FINISHED
Object Tuddenham E299727 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: Tuddenham | Statement: [Suffolk, containsSettlement, Tuddenham]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tuddenham
Context triple: [Suffolk, containsSettlement, Tuddenham]
  • A. Tuddenham chosen
    Tuddenham is a village and civil parish located in the county of Suffolk in eastern England.
  • B. Manton
    Manton is a neighborhood and village area located within Providence County in the state of Rhode Island.
  • C. Hannington
    Hannington is a small rural village in Wiltshire, England, known for its traditional English countryside setting and historic character.
  • D. Sydenham
    Sydenham is a suburban district in southeast London, England, known for its Victorian architecture, green spaces, and residential character.
  • E. Moston
    Moston is a residential district in north Manchester, England, known for its mix of traditional terraced housing, local parks, and community amenities.
  • 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_69ad857c97d88190b26f9b1c90839c77 completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69ada20d8f788190b05b8b6b5042bc1a completed March 8, 2026, 4:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69b1f8a4c1f08190a80efd190e4ed07f completed March 11, 2026, 11:20 p.m.
Created at: March 8, 2026, 3:03 p.m.