Triple

T8910016
Position Surface form Disambiguated ID Type / Status
Subject mainland Kent E212157 entity
Predicate hasMajorTown P316 FINISHED
Object Gravesend E42800 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: Gravesend | Statement: [mainland Kent, hasMajorTown, Gravesend]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gravesend
Context triple: [mainland Kent, hasMajorTown, Gravesend]
  • A. Gravesend
    Gravesend is a historic residential neighborhood in southern Brooklyn, New York City, known for its early Dutch colonial roots and diverse, largely working- and middle-class community.
  • B. Gravesend chosen
    Gravesend is a historic riverside town on the south bank of the River Thames in north-west Kent, England.
  • C. Sheerness Port
    Sheerness Port is a major deep-water port on the Isle of Sheppey in Kent, England, known for handling automotive imports, forest products, and other bulk cargo.
  • D. Richborough
    Richborough is a historic site in Kent, England, known for its significant Roman remains and its role as a key gateway to Roman Britain.
  • E. Sheerness
    Sheerness is a coastal town and port on the Isle of Sheppey in Kent, England, historically significant for its naval dockyard and maritime defenses.
  • 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_69ca839255248190b43984294abd92ae completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc65227d008190b13ba162d0b3c9d1 completed April 1, 2026, 12:21 a.m.
NED1 Entity disambiguation (via context triple) batch_69cfba36f8cc8190ab57ddc99b7219d1 completed April 3, 2026, 1:01 p.m.
Created at: March 30, 2026, 6:55 p.m.