Triple
T3658083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bergen op Zoom |
E77581
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object |
Lepelstraat
Lepelstraat is a village in the Dutch province of North Brabant that forms part of the municipality of Bergen op Zoom.
|
E377325
|
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: Lepelstraat | Statement: [Bergen op Zoom, hasPart, Lepelstraat]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lepelstraat Context triple: [Bergen op Zoom, hasPart, Lepelstraat]
-
A.
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.
-
B.
P.C. Hooftstraat
P.C. Hooftstraat is an upscale shopping street in Amsterdam known for its luxury boutiques and high-end international fashion brands.
-
C.
Domstraat
Domstraat is a historic street in the center of Utrecht, Netherlands, connecting key landmarks around the Dom Tower and cathedral.
-
D.
Raadhuisstraat
Raadhuisstraat is a central street in Amsterdam, Netherlands, known for connecting Dam Square to the Jordaan district and for its historic architecture and shops.
-
E.
Spuistraat
Spuistraat is a central street in Amsterdam known for its historic buildings, shops, and proximity to major city landmarks.
- 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: Lepelstraat Triple: [Bergen op Zoom, hasPart, Lepelstraat]
Generated description
Lepelstraat is a village in the Dutch province of North Brabant that forms part of the municipality of Bergen op Zoom.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Lepelstraat Target entity description: Lepelstraat is a village in the Dutch province of North Brabant that forms part of the municipality of Bergen op Zoom.
-
A.
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.
-
B.
P.C. Hooftstraat
P.C. Hooftstraat is an upscale shopping street in Amsterdam known for its luxury boutiques and high-end international fashion brands.
-
C.
Domstraat
Domstraat is a historic street in the center of Utrecht, Netherlands, connecting key landmarks around the Dom Tower and cathedral.
-
D.
Raadhuisstraat
Raadhuisstraat is a central street in Amsterdam, Netherlands, known for connecting Dam Square to the Jordaan district and for its historic architecture and shops.
-
E.
Spuistraat
Spuistraat is a central street in Amsterdam known for its historic buildings, shops, and proximity to major city landmarks.
- 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_69ad85def5cc8190863dccf55a18bebb |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc3d48a2081908ac0f76d548a53ee |
completed | March 8, 2026, 6:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b4884071c881909daae2f3c510d399 |
completed | March 13, 2026, 9:57 p.m. |
| NEDg | Description generation | batch_69b48ce33a208190bd7cf894a11497a1 |
completed | March 13, 2026, 10:17 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69b4aed7f4008190b5adbf3a89f4b5bd |
completed | March 14, 2026, 12:42 a.m. |
Created at: March 8, 2026, 3:24 p.m.