Triple

T4267971
Position Surface form Disambiguated ID Type / Status
Subject historic county of Kent E96870 entity
Predicate contains P35 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: [historic county of Kent, contains, Gravesend]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gravesend
Context triple: [historic county of Kent, contains, 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. Newhaven
    Newhaven is a historic coastal district of Edinburgh, Scotland, known for its former fishing village, harbor, and maritime heritage.
  • 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_69b34543f06c8190915ebb1a4574ffa9 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b34fce710481909d90ed4a3d150fde completed March 12, 2026, 11:44 p.m.
NED1 Entity disambiguation (via context triple) batch_69b5b79fe8c08190b4a9e4812babc78e completed March 14, 2026, 7:31 p.m.
Created at: March 12, 2026, 11:07 p.m.