Triple

T6631395
Position Surface form Disambiguated ID Type / Status
Subject Retford E149932 entity
Predicate hasPostTown P2711 FINISHED
Object RETFORD E149932 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: RETFORD | Statement: [Retford, hasPostTown, RETFORD]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RETFORD
Context triple: [Retford, hasPostTown, RETFORD]
  • A. Stopford
    Stopford refers to Lieutenant-General Sir Montagu Stopford, a British Army officer who played a key leadership role in the Burma Campaign of World War II, particularly noted for his command in the Southeast Asian theater.
  • B. Retford chosen
    Retford is a historic market town in the English county of Nottinghamshire, known for its traditional town center and transport links.
  • C. Durford
    Durford is a small settlement in West Sussex, England, situated in the countryside near the River Rother.
  • D. Metford
    Metford is a residential suburb in the city of Maitland in the Hunter Region of New South Wales, Australia.
  • E. Wentford
    Wentford is a surname that appears to be a variant or related form of the English surname Wentworth.
  • 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_69c687ee50048190aa151765bef16193 completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6afa6e52c8190943c86660da23c75 completed March 27, 2026, 4:26 p.m.
NED1 Entity disambiguation (via context triple) batch_69c6cbeef9f48190aea2e97a1f8735ee completed March 27, 2026, 6:26 p.m.
Created at: March 27, 2026, 1:59 p.m.