Triple

T29454084
Position Surface form Disambiguated ID Type / Status
Subject White Rock Promenade E747050 entity
Predicate adjacentTo P224 FINISHED
Object White Rock beach
White Rock beach is a popular coastal destination in White Rock, British Columbia, known for its long sandy shoreline, scenic ocean views, and nearby promenade.
E1908642 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: White Rock beach | Statement: [White Rock Promenade, adjacentTo, White Rock beach]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: White Rock beach
Triple: [White Rock Promenade, adjacentTo, White Rock beach]
Generated description
White Rock beach is a popular coastal destination in White Rock, British Columbia, known for its long sandy shoreline, scenic ocean views, and nearby promenade.

Provenance (5 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_69f0a7a230488190b44a97fe3d16f731 completed April 28, 2026, 12:27 p.m.
NER Named-entity recognition batch_69f66b6b17c48190899f49d33946738e completed May 2, 2026, 9:23 p.m.
NED1 Entity disambiguation (via context triple) batch_6a276ed03c3c8190a853339c08068ad8 completed June 9, 2026, 1:39 a.m.
NEDg Description generation batch_6a2772b62b348190b3d1bf268a901288 completed June 9, 2026, 1:56 a.m.
NED2 Entity disambiguation (via description) batch_6a2772eb8538819087415acface6f03c completed June 9, 2026, 1:56 a.m.
Created at: April 28, 2026, 3:35 p.m.