Triple

T19320187
Position Surface form Disambiguated ID Type / Status
Subject Lewes Assizes E483201 entity
Predicate locatedIn P40 FINISHED
Object Lewes 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: Lewes | Statement: [Lewes Assizes, locatedIn, Lewes]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lewes
Context triple: [Lewes Assizes, locatedIn, Lewes]
  • A. Lewes
    Lewes is a historic coastal town in southern Delaware, recognized as one of the earliest European settlements in the state and a popular gateway to nearby Atlantic beaches.
  • B. Lewes chosen
    Lewes is a historic market town in southeastern England known for its medieval architecture, castle, and famous Bonfire Night celebrations.
  • C. Dover
    Dover is a small town in eastern Dutchess County, New York, known for its rural character and location near the Connecticut border.
  • D. Dover
    Dover is a residential and educational neighborhood in western Singapore, known for its proximity to universities and polytechnics.
  • E. Dover
    Dover is a coastal town in southeast England best known for its white chalk cliffs and its strategic port facing the narrowest part of the English Channel.
  • 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_69d8e8d13e3c81909d91d1d5ec37c095 completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e60d87a0088190a60201b1f388089e completed April 20, 2026, 11:27 a.m.
Created at: April 10, 2026, 1:32 p.m.