Triple

T13261819
Position Surface form Disambiguated ID Type / Status
Subject Seaburn Beach E315815 entity
Predicate near P350 FINISHED
Object Roker Beach E322482 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: Roker Beach | Statement: [Seaburn Beach, near, Roker Beach]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Roker Beach
Context triple: [Seaburn Beach, near, Roker Beach]
  • A. Roker Beach chosen
    Roker Beach is a popular seaside destination in Sunderland, England, known for its sandy shore, promenade, and views of the North Sea.
  • B. Seaside Beach
    Seaside Beach is a popular sandy shoreline in Seaside, Oregon, known for its family-friendly promenade, expansive beachfront, and classic Pacific Northwest coastal scenery.
  • C. Harrington Beach
    Harrington Beach is a scenic lakeside recreational area known for its sandy shoreline, walking trails, and outdoor leisure activities.
  • D. Jetty Beach
    Jetty Beach is a popular sheltered swimming and recreation beach located near the historic jetty precinct in Coffs Harbour, New South Wales, Australia.
  • E. Sandhaven Beach
    Sandhaven Beach is a popular sandy seaside destination in South Shields, England, known for its wide golden shore, clean waters, and family-friendly promenade.
  • 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_69d806b1d9ac8190852c5571d5bd5f0f completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d9901b380881909e6520fbb6811084 completed April 11, 2026, 12:04 a.m.
NED1 Entity disambiguation (via context triple) batch_69fbc311b1248190b9ceb2854e93171a completed May 6, 2026, 10:39 p.m.
Created at: April 9, 2026, 9:25 p.m.