Triple

T10430385
Position Surface form Disambiguated ID Type / Status
Subject Mise of Lewes agreement E245896 entity
Predicate location P40 FINISHED
Object Lewes E155214 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: Lewes | Statement: [Mise of Lewes agreement, location, Lewes]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lewes
Context triple: [Mise of Lewes agreement, location, 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 the capital city of the U.S. state of Delaware, known for its historic district, government institutions, and proximity to Delaware Bay.
  • E. Dover
    Dover is a residential and educational neighborhood in western Singapore, known for its proximity to universities and polytechnics.
  • 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_69d381bf3dc08190bf35a2643e4e8f22 completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4ea62d6448190a7f5b785467824cf completed April 7, 2026, 11:28 a.m.
NED1 Entity disambiguation (via context triple) batch_69d89f8a5b00819080c303bb0fc82f5a completed April 10, 2026, 6:58 a.m.
Created at: April 6, 2026, 12:13 p.m.