Triple

T19833911
Position Surface form Disambiguated ID Type / Status
Subject Roker E476533 entity
Predicate hasFeature P182 FINISHED
Object Roker Beach 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: Roker Beach | Statement: [Roker, hasFeature, Roker Beach]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Roker Beach
Context triple: [Roker, hasFeature, 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. Belmar Beach
    Belmar Beach is a popular public oceanfront destination on the Jersey Shore known for its wide sandy shoreline, boardwalk, and seasonal recreational activities.
  • 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_69d8e51c7c188190b926f3a2a7b5f881 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e656d0347c8190b586c7fe01b61e97 completed April 20, 2026, 4:39 p.m.
Created at: April 10, 2026, 1:50 p.m.