Triple
T5058364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metro line 51 |
E113961
|
entity |
| Predicate | terminus |
P388
|
FINISHED |
| Object |
Westwijk
Westwijk is a residential district in Amstelveen, Netherlands, served as the southern terminus of Amsterdam’s former metro line 51.
|
E921368
|
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: Westwijk | Statement: [Metro line 51, terminus, Westwijk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Westwijk Context triple: [Metro line 51, terminus, Westwijk]
-
A.
Winterswijk
Winterswijk is a town in the eastern Netherlands known for its rural landscape, textile-industry history, and location near the German border.
-
B.
Waalwijk
Waalwijk is a town and municipality in the southern Netherlands known historically for its leather and shoe industry.
-
C.
Nieuwendijk
Nieuwendijk is one of Amsterdam’s oldest and busiest shopping streets, running through the historic city center near Dam Square.
-
D.
Steenwijk
Steenwijk is a historic town in the Dutch province of Overijssel, known for its medieval center and role as a regional hub in the north of the province.
-
E.
Zwijndrecht
Zwijndrecht is a Dutch town and municipality located in the western Netherlands, known for its position along the rivers near the city of Dordrecht.
- 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: Westwijk Triple: [Metro line 51, terminus, Westwijk]
Generated description
Westwijk is a residential district in Amstelveen, Netherlands, served as the southern terminus of Amsterdam’s former metro line 51.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Westwijk Target entity description: Westwijk is a residential district in Amstelveen, Netherlands, served as the southern terminus of Amsterdam’s former metro line 51.
-
A.
Winterswijk
Winterswijk is a town in the eastern Netherlands known for its rural landscape, textile-industry history, and location near the German border.
-
B.
Waalwijk
Waalwijk is a town and municipality in the southern Netherlands known historically for its leather and shoe industry.
-
C.
Nieuwendijk
Nieuwendijk is one of Amsterdam’s oldest and busiest shopping streets, running through the historic city center near Dam Square.
-
D.
Steenwijk
Steenwijk is a historic town in the Dutch province of Overijssel, known for its medieval center and role as a regional hub in the north of the province.
-
E.
Zwijndrecht
Zwijndrecht is a Dutch town and municipality located in the western Netherlands, known for its position along the rivers near the city of Dordrecht.
- 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_69bd443aa1f88190abb992d138f2cf42 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74523434819092b8b15992073b5b |
completed | March 20, 2026, 4:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e5561714a081909cbf1cc7d5d0ac0a |
completed | April 19, 2026, 10:24 p.m. |
| NEDg | Description generation | batch_69e562bb085c8190942766d12d838798 |
completed | April 19, 2026, 11:18 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69e569f0e6948190b285ca84aca03771 |
completed | April 19, 2026, 11:49 p.m. |
Created at: March 20, 2026, 1:38 p.m.