Triple

T33087650
Position Surface form Disambiguated ID Type / Status
Subject Dordrecht city canal network E846685 entity
Predicate hasPart P35 FINISHED
Object Nieuwe Haven canal
Nieuwe Haven canal is a historic waterway in the Dutch city of Dordrecht, lined with old warehouses and houses and forming part of the city’s traditional harbor area.
E2035623 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: Nieuwe Haven canal | Statement: [Dordrecht city canal network, hasPart, Nieuwe Haven canal]
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: Nieuwe Haven canal
Triple: [Dordrecht city canal network, hasPart, Nieuwe Haven canal]
Generated description
Nieuwe Haven canal is a historic waterway in the Dutch city of Dordrecht, lined with old warehouses and houses and forming part of the city’s traditional harbor area.

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_69f34954d46c8190a04a159cc5f99efd completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6d6237ac4819099e3408032d6d45f completed May 3, 2026, 4:59 a.m.
NED1 Entity disambiguation (via context triple) batch_6a34f024d5fc81908bd7f0e15219db40 completed June 19, 2026, 7:30 a.m.
NEDg Description generation batch_6a34f36df55881909fcc31f8e57e3d37 completed June 19, 2026, 7:44 a.m.
NED2 Entity disambiguation (via description) batch_6a34f52a88108190a0d7a1c0e1d70488 completed June 19, 2026, 7:52 a.m.
Created at: May 1, 2026, 1:26 a.m.