Triple

T22885810
Position Surface form Disambiguated ID Type / Status
Subject Mansfield Wesleyans E567600 entity
Predicate location P40 FINISHED
Object Mansfield NE NERFINISHED

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: Mansfield | Statement: [Mansfield Wesleyans, location, Mansfield]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mansfield
Context triple: [Mansfield Wesleyans, location, Mansfield]
  • A. Mansfield
    Mansfield is a historic Scottish territorial designation traditionally linked to the noble House of Murray.
  • B. Mansfield chosen
    Mansfield is a large market town in Nottinghamshire, England, known historically for its coal mining industry and proximity to Sherwood Forest.
  • C. Mansfield
    Mansfield is a small borough in northern Pennsylvania known for its rural setting and the presence of Mansfield University of Pennsylvania.
  • D. Mansfield
    Mansfield is a surname of English origin borne by various notable individuals across politics, arts, and other fields.
  • E. Mansfield
    Mansfield is a rural town in northeastern Victoria, Australia, known as a gateway to the Victorian High Country and nearby alpine resorts.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e2458a92ec81908fc1cd5f6407d2ab completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17fc0cdb081908107d40069d9735f completed April 29, 2026, 3:49 a.m.
Created at: April 17, 2026, 3:40 p.m.