Triple
T2646799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dom Square |
E53802
|
entity |
| Predicate | hasNearbyStreet |
P8235
|
FINISHED |
| Object |
Servetstraat
Servetstraat is a small historic street located near Dom Square in the center of Utrecht, Netherlands.
|
E296237
|
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: Servetstraat | Statement: [Dom Square, hasNearbyStreet, Servetstraat]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Servetstraat Context triple: [Dom Square, hasNearbyStreet, Servetstraat]
-
A.
Kalverstraat
Kalverstraat is one of Amsterdam’s busiest and most famous shopping streets, known for its dense concentration of retail stores and central location.
-
B.
Paleisstraat
Paleisstraat is a central street in Amsterdam that runs alongside the Royal Palace and links Dam Square with the Jordaan area.
-
C.
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.
-
D.
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.
-
E.
Domstraat
Domstraat is a historic street in the center of Utrecht, Netherlands, connecting key landmarks around the Dom Tower and cathedral.
- 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: Servetstraat Triple: [Dom Square, hasNearbyStreet, Servetstraat]
Generated description
Servetstraat is a small historic street located near Dom Square in the center of Utrecht, Netherlands.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Servetstraat Target entity description: Servetstraat is a small historic street located near Dom Square in the center of Utrecht, Netherlands.
-
A.
Kalverstraat
Kalverstraat is one of Amsterdam’s busiest and most famous shopping streets, known for its dense concentration of retail stores and central location.
-
B.
Paleisstraat
Paleisstraat is a central street in Amsterdam that runs alongside the Royal Palace and links Dam Square with the Jordaan area.
-
C.
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.
-
D.
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.
-
E.
Domstraat
Domstraat is a historic street in the center of Utrecht, Netherlands, connecting key landmarks around the Dom Tower and cathedral.
- 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_69ab495e192081909c77b622e8e7e15a |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd919bf2c81908feb768f3391e985 |
completed | March 7, 2026, 7:51 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69afc02acc048190812d7d2d8b59058a |
completed | March 10, 2026, 6:54 a.m. |
| NEDg | Description generation | batch_69afc0a3dcb4819098e922989fb8165c |
completed | March 10, 2026, 6:56 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69afc10deaa4819082ad29756b651480 |
completed | March 10, 2026, 6:58 a.m. |
Created at: March 6, 2026, 9:53 p.m.