Triple

T17702014
Position Surface form Disambiguated ID Type / Status
Subject Lower Town of Brussels E441328 entity
Predicate contains P35 FINISHED
Object Rue de l’Écuyer
Rue de l’Écuyer is a historic street in central Brussels, Belgium, known for its proximity to the Grand Place and its mix of shops, offices, and traditional city architecture.
E1257431 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: Rue de l’Écuyer | Statement: [Lower Town of Brussels, contains, Rue de l’Écuyer]
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: Rue de l’Écuyer
Triple: [Lower Town of Brussels, contains, Rue de l’Écuyer]
Generated description
Rue de l’Écuyer is a historic street in central Brussels, Belgium, known for its proximity to the Grand Place and its mix of shops, offices, and traditional city architecture.

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_69d8b9ea20b48190ace88bb46b01e6a9 completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e4715c3980819094b080a871df1100 completed April 19, 2026, 6:08 a.m.
NED1 Entity disambiguation (via context triple) batch_6a36ae27aa9881909fdfd5e384b4003d completed June 20, 2026, 3:13 p.m.
NEDg Description generation batch_6a36af0ecea8819092b60c42572f3865 completed June 20, 2026, 3:17 p.m.
NED2 Entity disambiguation (via description) batch_6a36afaee2b88190b603b07a7700efa2 completed June 20, 2026, 3:20 p.m.
Created at: April 10, 2026, 10:05 a.m.