Triple

T18463414
Position Surface form Disambiguated ID Type / Status
Subject Bucks Horn Oak E451093 entity
Predicate hasNearbySettlement P4647 FINISHED
Object Binsted NE NERFINISHED

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: Binsted | Statement: [Bucks Horn Oak, hasNearbySettlement, Binsted]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Binsted
Context triple: [Bucks Horn Oak, hasNearbySettlement, Binsted]
  • A. Binsted chosen
    Binsted is a rural civil parish and village in East Hampshire, England, known for its countryside setting and historic church.
  • B. Binsted
    Binsted is a small rural village in West Sussex, England, known for its historic parish church of the Holy Cross and its surrounding countryside.
  • C. Bildeston
    Bildeston is a historic village and civil parish located in the county of Suffolk in eastern England.
  • D. South Bersted
    South Bersted is a residential area and suburb forming part of the seaside town of Bognor Regis on the south coast of England.
  • E. Balsthal
    Balsthal is a Swiss municipality in the canton of Solothurn, known for its industrial history and location in the Jura Mountains.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8d38345688190b565eac2e4cd7935 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e52a8190508190a74b1d3482364905 completed April 19, 2026, 7:18 p.m.
Created at: April 10, 2026, 11:33 a.m.