Triple

T8971289
Position Surface form Disambiguated ID Type / Status
Subject Bournemouth Beach E214271 entity
Predicate locatedIn P40 FINISHED
Object Bournemouth E38127 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: Bournemouth | Statement: [Bournemouth Beach, locatedIn, Bournemouth]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bournemouth
Context triple: [Bournemouth Beach, locatedIn, Bournemouth]
  • A. Bournemouth chosen
    Bournemouth is a large coastal resort town on England’s south coast, known for its sandy beaches, tourism, and role as a regional commercial and transport hub.
  • B. Poole
    Poole is a coastal town and seaport in Dorset, England, known for its large natural harbour and maritime activities.
  • C. Bristol
    Bristol is a historic port city in southwest England known for its maritime heritage, vibrant cultural scene, and distinctive Georgian and Victorian architecture.
  • D. Bristol
    Bristol is a city in central Connecticut known for being the home of ESPN and for its historic clock-making industry.
  • E. Bristol
    Bristol is a city in central Connecticut known historically for its clock-making industry and as the longtime home of ESPN’s headquarters.
  • 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_69ca839dbf608190a2f5990477115d29 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc67672c108190919ae6ca69b6291f completed April 1, 2026, 12:31 a.m.
NED1 Entity disambiguation (via context triple) batch_69d0c6d4a5d08190832f41dd9dc82f41 completed April 4, 2026, 8:07 a.m.
Created at: March 30, 2026, 7:02 p.m.