Triple

T16956687
Position Surface form Disambiguated ID Type / Status
Subject siege of Dover (1216–1217) E411323 entity
Predicate location P40 FINISHED
Object Dover E31236 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: Dover | Statement: [siege of Dover (1216–1217), location, Dover]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dover
Context triple: [siege of Dover (1216–1217), location, Dover]
  • A. Dover
    Dover is one of the oldest permanent European settlements in what is now the U.S. state of New Hampshire, historically significant as an early colonial town and port.
  • B. 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.
  • 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 chosen
    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 (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_69d886c9c9d481909afe222093641cae completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3d01c7b408190b5a2b6c62b050b76 completed April 18, 2026, 6:40 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00dc06e6b481908d8032f5772762c9 completed May 10, 2026, 7:27 p.m.
Created at: April 10, 2026, 5:31 a.m.