Triple

T13336232
Position Surface form Disambiguated ID Type / Status
Subject River Len E317699 entity
Predicate hasNearbySettlement P4647 FINISHED
Object Bearsted E905589 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: Bearsted | Statement: [River Len, hasNearbySettlement, Bearsted]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bearsted
Context triple: [River Len, hasNearbySettlement, Bearsted]
  • A. Bearsted chosen
    Bearsted is a village and civil parish in the borough of Maidstone in Kent, England, known for its historic village green and commuter links to London.
  • B. Burgstaaken
    Burgstaaken is a small harbour district and marina area on the island of Fehmarn in northern Germany, known for its fishing, tourism, and maritime activities.
  • C. Stisted
    Stisted is an English surname most notably associated with Henry William Stisted, a 19th-century British Army officer and colonial administrator.
  • D. Bresee
    Bresee is a surname most notably associated with Phineas F. Bresee, a key founder of the Church of the Nazarene.
  • E. Bristelmestune
    Bristelmestune is the early recorded medieval name for the English coastal town later known as Brighthelmstone and now as Brighton.
  • 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_69d806b5a3c08190b42c267fb092f98a completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d99d00b75c8190af98784c7df904c8 completed April 11, 2026, 12:59 a.m.
NED1 Entity disambiguation (via context triple) batch_69f7267132488190a62930e98be70640 completed May 3, 2026, 10:41 a.m.
Created at: April 9, 2026, 9:31 p.m.