Triple
T6997103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grote Markt (Haarlem) |
E162242
|
entity |
| Predicate | adjacentStreet |
P8235
|
FINISHED |
| Object |
Koningstraat (Haarlem)
Koningstraat (Haarlem) is a central shopping and pedestrian street in the historic heart of Haarlem, Netherlands.
|
E639655
|
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: Koningstraat (Haarlem) | Statement: [Grote Markt (Haarlem), adjacentStreet, Koningstraat (Haarlem)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Koningstraat (Haarlem) Context triple: [Grote Markt (Haarlem), adjacentStreet, Koningstraat (Haarlem)]
-
A.
Kruisstraat (Haarlem)
Kruisstraat (Haarlem) is a street in the historic center of Haarlem in the Netherlands, located near the city’s main square.
-
B.
Koningsstraat
Koningsstraat is a major central street in Brussels, Belgium, known for its straight, ceremonial layout and its role connecting key royal and administrative landmarks.
-
C.
Korte Nieuwstraat
Korte Nieuwstraat is a historic street in the center of Utrecht, Netherlands, located just off the city’s prominent Dom Square.
-
D.
Heemstedestraat
Heemstedestraat is a metro station in Amsterdam that serves as a stop on the city’s rapid transit network.
-
E.
Lepelstraat
Lepelstraat is a village in the Dutch province of North Brabant that forms part of the municipality of Bergen op Zoom.
- 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: Koningstraat (Haarlem) Triple: [Grote Markt (Haarlem), adjacentStreet, Koningstraat (Haarlem)]
Generated description
Koningstraat (Haarlem) is a central shopping and pedestrian street in the historic heart of Haarlem, Netherlands.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Koningstraat (Haarlem) Target entity description: Koningstraat (Haarlem) is a central shopping and pedestrian street in the historic heart of Haarlem, Netherlands.
-
A.
Kruisstraat (Haarlem)
Kruisstraat (Haarlem) is a street in the historic center of Haarlem in the Netherlands, located near the city’s main square.
-
B.
Koningsstraat
Koningsstraat is a major central street in Brussels, Belgium, known for its straight, ceremonial layout and its role connecting key royal and administrative landmarks.
-
C.
Korte Nieuwstraat
Korte Nieuwstraat is a historic street in the center of Utrecht, Netherlands, located just off the city’s prominent Dom Square.
-
D.
Heemstedestraat
Heemstedestraat is a metro station in Amsterdam that serves as a stop on the city’s rapid transit network.
-
E.
Lepelstraat
Lepelstraat is a village in the Dutch province of North Brabant that forms part of the municipality of Bergen op Zoom.
- 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_69c68857ffc08190857dc62cd5253777 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dbedafa48190af0d2b47e3a1e17e |
completed | March 27, 2026, 7:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7943400d08190ba5774e5d45e7e27 |
completed | March 28, 2026, 8:41 a.m. |
| NEDg | Description generation | batch_69c794ddbb688190b197a934c0afaea0 |
completed | March 28, 2026, 8:44 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69c79531e0408190bbacba54914393f9 |
completed | March 28, 2026, 8:45 a.m. |
Created at: March 27, 2026, 2:32 p.m.