Triple

T26979550
Position Surface form Disambiguated ID Type / Status
Subject Wapper square E679557 entity
Predicate hasNearbyStreet P8235 FINISHED
Object Schuttershofstraat
Schuttershofstraat is a well-known shopping street in the center of Antwerp, Belgium, noted for its luxury boutiques and proximity to major city landmarks.
E1765788 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: Schuttershofstraat | Statement: [Wapper square, hasNearbyStreet, Schuttershofstraat]
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: Schuttershofstraat
Triple: [Wapper square, hasNearbyStreet, Schuttershofstraat]
Generated description
Schuttershofstraat is a well-known shopping street in the center of Antwerp, Belgium, noted for its luxury boutiques and proximity to major city landmarks.

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_69eeeb507a7081909d516e1fa08b7d29 completed April 27, 2026, 4:51 a.m.
NER Named-entity recognition batch_69f62155628081908c4189b988951ad6 completed May 2, 2026, 4:07 p.m.
NED1 Entity disambiguation (via context triple) batch_6a129c86aeb4819096af38a020a65a6a completed May 24, 2026, 6:36 a.m.
NEDg Description generation batch_6a129df2f3f08190a92f82754b29a06a completed May 24, 2026, 6:42 a.m.
NED2 Entity disambiguation (via description) batch_6a129e7b3f508190b7cc7b6f40177927 completed May 24, 2026, 6:45 a.m.
Created at: April 27, 2026, 6:44 a.m.