Triple

T22626477
Position Surface form Disambiguated ID Type / Status
Subject Moston E558433 entity
Predicate hasName P744 FINISHED
Object Moston 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: Moston | Statement: [Moston, hasName, Moston]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Moston
Context triple: [Moston, hasName, Moston]
  • A. Moston
    Moston is a small rural village in Cheshire, England, situated near the town of Middlewich.
  • B. Moston
    Moston is a residential district in north Manchester, England, known for its mix of traditional terraced housing, local parks, and community amenities.
  • C. Manton
    Manton is a small unincorporated rural community in Tehama County, California, known for its agricultural setting and proximity to the Cascade Range foothills.
  • D. Manton
    Manton is a small unincorporated community located in Nelson County, Kentucky, known for its rural setting within the state's central region.
  • E. Manton
    Manton is a suburb in the Greater Darwin region of the Northern Territory, Australia, known for its rural character and proximity to Manton Dam.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide. chosen

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_69e245467d9881908d6985bd0db7a1f1 completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f16e3d55b081908930ebff4372154f completed April 29, 2026, 2:34 a.m.
Created at: April 17, 2026, 3:01 p.m.