Triple

T16557614
Position Surface form Disambiguated ID Type / Status
Subject Seacombe E402250 entity
Predicate near P350 FINISHED
Object Worth Matravers E85961 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: Worth Matravers | Statement: [Seacombe, near, Worth Matravers]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Worth Matravers
Context triple: [Seacombe, near, Worth Matravers]
  • A. Worth Matravers chosen
    Worth Matravers is a small coastal village on the Isle of Purbeck in Dorset, England, known for its historic stone cottages, quarries, and scenic walking paths along the Jurassic Coast.
  • B. Thrupp
    Thrupp is a small canal-side village in Oxfordshire, England, known for its historic wharf and picturesque setting along the Oxford Canal.
  • C. Hatherleigh
    Hatherleigh is a small rural locality in South Australia situated within the Wattle Range Council area.
  • D. Bewbush
    Bewbush is a residential neighbourhood and housing estate in the town of Crawley in West Sussex, England.
  • E. Swanmore
    Swanmore is a rural village and civil parish in Hampshire, England, known for its countryside setting and residential character.
  • 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_69d8838648088190acf97ef11fc3f61b completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e34fca6db8819098c4f3919bb052d8 completed April 18, 2026, 9:32 a.m.
NED1 Entity disambiguation (via context triple) batch_6a009d2bbe9c81909031d79f93faca6a completed May 10, 2026, 2:58 p.m.
Created at: April 10, 2026, 5:15 a.m.