Triple
T3109536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jordaan |
E64916
|
entity |
| Predicate | traversedBy |
P225
|
FINISHED |
| Object |
Rozenstraat
Rozenstraat is a street in Amsterdam’s historic Jordaan neighborhood, known for its traditional canal-side architecture and local character.
|
E339986
|
NE FINISHED |
How this triple was built (4 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: Rozenstraat | Statement: [Jordaan, traversedBy, Rozenstraat]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rozenstraat Context triple: [Jordaan, traversedBy, Rozenstraat]
-
A.
Spuistraat
Spuistraat is a central street in Amsterdam known for its historic buildings, shops, and proximity to major city landmarks.
-
B.
Domstraat
Domstraat is a historic street in the center of Utrecht, Netherlands, connecting key landmarks around the Dom Tower and cathedral.
-
C.
Vijzelstraat
Vijzelstraat is a major street in central Amsterdam, Netherlands, running between the city’s historic canals and serving as an important traffic and commercial route.
-
D.
Utrechtsestraat
Utrechtsestraat is a well-known shopping and dining street in central Amsterdam, noted for its historic canalside setting and mix of boutiques, cafés, and restaurants.
-
E.
Servetstraat
Servetstraat is a small historic street located near Dom Square in the center of Utrecht, Netherlands.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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: Rozenstraat Triple: [Jordaan, traversedBy, Rozenstraat]
Generated description
Rozenstraat is a street in Amsterdam’s historic Jordaan neighborhood, known for its traditional canal-side architecture and local character.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Rozenstraat Target entity description: Rozenstraat is a street in Amsterdam’s historic Jordaan neighborhood, known for its traditional canal-side architecture and local character.
-
A.
Spuistraat
Spuistraat is a central street in Amsterdam known for its historic buildings, shops, and proximity to major city landmarks.
-
B.
Domstraat
Domstraat is a historic street in the center of Utrecht, Netherlands, connecting key landmarks around the Dom Tower and cathedral.
-
C.
Vijzelstraat
Vijzelstraat is a major street in central Amsterdam, Netherlands, running between the city’s historic canals and serving as an important traffic and commercial route.
-
D.
Utrechtsestraat
Utrechtsestraat is a well-known shopping and dining street in central Amsterdam, noted for its historic canalside setting and mix of boutiques, cafés, and restaurants.
-
E.
Servetstraat
Servetstraat is a small historic street located near Dom Square in the center of Utrecht, Netherlands.
- F. None of above. chosen
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_69ad857eeaf48190b34ebfdaa7a264cf |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada2a0ab2481908db50738ec3ad0fb |
completed | March 8, 2026, 4:24 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b276df42048190bcb79277a28f866a |
completed | March 12, 2026, 8:18 a.m. |
| NEDg | Description generation | batch_69b27ab4bcb081909a59f41449f7bde8 |
completed | March 12, 2026, 8:35 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69b27b1ab6848190bebc7b02ce67071c |
completed | March 12, 2026, 8:36 a.m. |
Created at: March 8, 2026, 3:04 p.m.