Triple

T26567560
Position Surface form Disambiguated ID Type / Status
Subject Hellegatsplein junction area E666729 entity
Predicate crossesWaterVia P15424 FINISHED
Object Hellegats Bridge
Hellegats Bridge is a major Dutch road bridge in South Holland that carries traffic across the water between the Hellegatsplein junction and the surrounding islands.
E1762276 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: Hellegats Bridge | Statement: [Hellegatsplein junction area, crossesWaterVia, Hellegats Bridge]
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: Hellegats Bridge
Triple: [Hellegatsplein junction area, crossesWaterVia, Hellegats Bridge]
Generated description
Hellegats Bridge is a major Dutch road bridge in South Holland that carries traffic across the water between the Hellegatsplein junction and the surrounding islands.

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_69ee9cfa21c081909e4e36e087debfc6 completed April 26, 2026, 11:17 p.m.
NER Named-entity recognition batch_69f6576569bc8190b0eb1f0fde785c14 completed May 2, 2026, 7:58 p.m.
NED1 Entity disambiguation (via context triple) batch_6a12535a16e48190bdfe798f281fd4ec completed May 24, 2026, 1:24 a.m.
NEDg Description generation batch_6a12574c06788190951ce13779ea5ba8 completed May 24, 2026, 1:41 a.m.
NED2 Entity disambiguation (via description) batch_6a125793327881908c67b67f1bdf19e6 completed May 24, 2026, 1:42 a.m.
Created at: April 27, 2026, 1:56 a.m.