Triple

T32549261
Position Surface form Disambiguated ID Type / Status
Subject Oudezijds Voorburgwal E831930 entity
Predicate crosses P416 FINISHED
Object Oude Hoogstraat
Oude Hoogstraat is a historic street in central Amsterdam, known for its old buildings, canalside location, and proximity to the city’s medieval core and Red Light District.
E2015958 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: Oude Hoogstraat | Statement: [Oudezijds Voorburgwal, crosses, Oude Hoogstraat]
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: Oude Hoogstraat
Triple: [Oudezijds Voorburgwal, crosses, Oude Hoogstraat]
Generated description
Oude Hoogstraat is a historic street in central Amsterdam, known for its old buildings, canalside location, and proximity to the city’s medieval core and Red Light District.

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_69f34925fd08819084cfe4ec566cb704 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6c5c5a8c4819088fcf00fcbcc7f51 completed May 3, 2026, 3:49 a.m.
NED1 Entity disambiguation (via context triple) batch_6a34929004dc8190a4493dc9c805e578 completed June 19, 2026, 12:51 a.m.
NEDg Description generation batch_6a34930dfbfc819080a4598618be05d5 completed June 19, 2026, 12:53 a.m.
NED2 Entity disambiguation (via description) batch_6a3493c4efb881909c333ffbe0642910 completed June 19, 2026, 12:56 a.m.
Created at: May 1, 2026, 1:02 a.m.