Triple
T13563778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zutphen |
E323979
|
entity |
| Predicate | hasLandmark |
P105
|
FINISHED |
| Object |
Bourgonje Tower
Bourgonje Tower is a historic medieval defensive tower and notable architectural landmark in the Dutch city of Zutphen.
|
E1048580
|
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: Bourgonje Tower | Statement: [Zutphen, hasLandmark, Bourgonje Tower]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bourgonje Tower Context triple: [Zutphen, hasLandmark, Bourgonje Tower]
-
A.
Heuturm
Heuturm is one of the historic defensive towers incorporated into Lucerne’s medieval Musegg Wall in Switzerland.
-
B.
Oldehove tower
Oldehove tower is a historic, unfinished and leaning medieval church tower in the Dutch city of Leeuwarden, known as a prominent local landmark.
-
C.
Westertoren
Westertoren is the iconic church tower of Amsterdam’s Westerkerk, renowned as one of the city’s most recognizable landmarks overlooking the historic canal district.
-
D.
Kronenburgertoren
Kronenburgertoren is a historic medieval city tower in Nijmegen, Netherlands, known as a prominent remnant of the old city fortifications.
-
E.
Jaro Belfry
Jaro Belfry is a notable tower structure located in the town of Jaro, often recognized for its historical and architectural significance.
- 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: Bourgonje Tower Triple: [Zutphen, hasLandmark, Bourgonje Tower]
Generated description
Bourgonje Tower is a historic medieval defensive tower and notable architectural landmark in the Dutch city of Zutphen.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Bourgonje Tower Target entity description: Bourgonje Tower is a historic medieval defensive tower and notable architectural landmark in the Dutch city of Zutphen.
-
A.
Heuturm
Heuturm is one of the historic defensive towers incorporated into Lucerne’s medieval Musegg Wall in Switzerland.
-
B.
Oldehove tower
Oldehove tower is a historic, unfinished and leaning medieval church tower in the Dutch city of Leeuwarden, known as a prominent local landmark.
-
C.
Westertoren
Westertoren is the iconic church tower of Amsterdam’s Westerkerk, renowned as one of the city’s most recognizable landmarks overlooking the historic canal district.
-
D.
Kronenburgertoren
Kronenburgertoren is a historic medieval city tower in Nijmegen, Netherlands, known as a prominent remnant of the old city fortifications.
-
E.
Jaro Belfry
Jaro Belfry is a notable tower structure located in the town of Jaro, often recognized for its historical and architectural significance.
- 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_69d8076830b48190910a902bae5888e2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb00bbe848190bb33efe2af528295 |
completed | April 12, 2026, 2:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f76bb1ef508190ab587bd2aa34795b |
completed | May 3, 2026, 3:37 p.m. |
| NEDg | Description generation | batch_69f77640b5308190aaa50e8d5d871832 |
completed | May 3, 2026, 4:22 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69f778f01700819099c3e9cbc84f29e4 |
completed | May 3, 2026, 4:33 p.m. |
Created at: April 9, 2026, 9:47 p.m.