Triple

T23334143
Position Surface form Disambiguated ID Type / Status
Subject Masham E591527 entity
Predicate hasPostTown P2711 FINISHED
Object RIPON 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: RIPON | Statement: [Masham, hasPostTown, RIPON]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RIPON
Context triple: [Masham, hasPostTown, RIPON]
  • A. RIPON chosen
    RIPON is a historic cathedral city in North Yorkshire, England, known for Ripon Cathedral and its traditional market town character.
  • B. City of Ripon
    The City of Ripon is a historic cathedral city in North Yorkshire, England, known for its ancient traditions, including the nightly ceremony of the hornblower.
  • C. Ripon, Wisconsin
    Ripon, Wisconsin is a small city in central Wisconsin historically recognized as the birthplace of the Republican Party in the United States.
  • D. Parham
    Parham is a surname most notably associated with Charles F. Parham, an early leader in the Pentecostal Christian movement.
  • E. Parham
    Parham is a small rural community located within the township of Central Frontenac in eastern Ontario, Canada.
  • 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_69e25d20156c81908c5c53195bd9c738 completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f197efd98c819083635a2b8440f3eb completed April 29, 2026, 5:32 a.m.
Created at: April 17, 2026, 5:16 p.m.