Triple

T13796907
Position Surface form Disambiguated ID Type / Status
Subject Mansell E331539 entity
Predicate hasVariant P455 FINISHED
Object Mansfield E597507 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: Mansfield | Statement: [Mansell, hasVariant, Mansfield]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mansfield
Context triple: [Mansell, hasVariant, Mansfield]
  • A. Mansfield
    Mansfield is a large market town in Nottinghamshire, England, known historically for its coal mining industry and proximity to Sherwood Forest.
  • B. Mansfield
    Mansfield is a suburban city in the Dallas–Fort Worth metropolitan area of North Texas, known for its residential communities, schools, and family-oriented amenities.
  • 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 chosen
    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 (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_69d81c58feb08190a77bca8bf7d6d20f completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de025be1f08190aac525d72d7dc0c3 completed April 14, 2026, 9:01 a.m.
NED1 Entity disambiguation (via context triple) batch_69f7b086d6d48190b823ed0a4403fbc5 completed May 3, 2026, 8:31 p.m.
Created at: April 9, 2026, 10:11 p.m.