Triple

T32590100
Position Surface form Disambiguated ID Type / Status
Subject Pender Harbour E833039 entity
Predicate hasBay P35 FINISHED
Object Madeira Park harbour
Madeira Park harbour is a sheltered coastal inlet and marina area within Pender Harbour on British Columbia’s Sunshine Coast, known for boating, fishing, and waterfront recreation.
E2013589 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: Madeira Park harbour | Statement: [Pender Harbour, hasBay, Madeira Park harbour]
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: Madeira Park harbour
Triple: [Pender Harbour, hasBay, Madeira Park harbour]
Generated description
Madeira Park harbour is a sheltered coastal inlet and marina area within Pender Harbour on British Columbia’s Sunshine Coast, known for boating, fishing, and waterfront recreation.

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_69f34929ff648190aded9424aa7564ae completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6c67138e8819099aa4ded014143ba completed May 3, 2026, 3:52 a.m.
NED1 Entity disambiguation (via context triple) batch_6a347baa865481908c792a8fa01b3135 completed June 18, 2026, 11:13 p.m.
NEDg Description generation batch_6a347d37291c81909209d51020e6a749 completed June 18, 2026, 11:20 p.m.
NED2 Entity disambiguation (via description) batch_6a3480fc7ec88190a87901bbb2c0e3af completed June 18, 2026, 11:36 p.m.
Created at: May 1, 2026, 1:05 a.m.