Triple
T5157937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oud-Zuid |
E116359
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object |
Stadionweg
Stadionweg is a major street in Amsterdam’s Oud-Zuid district, known for its residential character and early 20th-century architecture.
|
E498348
|
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: Stadionweg | Statement: [Oud-Zuid, contains, Stadionweg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Stadionweg Context triple: [Oud-Zuid, contains, Stadionweg]
-
A.
Scheveningseweg
Scheveningseweg is a major historic road in The Hague, Netherlands, connecting the city center with the seaside district of Scheveningen.
-
B.
Bezuidenhoutseweg
Bezuidenhoutseweg is a major street in The Hague, Netherlands, known for its government buildings, offices, and proximity to key city landmarks.
-
C.
Spuistraat
Spuistraat is a central street in Amsterdam known for its historic buildings, shops, and proximity to major city landmarks.
-
D.
Spaklerweg
Spaklerweg is a metro station in Amsterdam that serves as a stop on the city’s rapid transit network.
-
E.
Buiksloterweg
Buiksloterweg is a neighborhood and ferry landing on the northern bank of the IJ in Amsterdam, serving as a key access point between Amsterdam-Noord and the city center.
- 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: Stadionweg Triple: [Oud-Zuid, contains, Stadionweg]
Generated description
Stadionweg is a major street in Amsterdam’s Oud-Zuid district, known for its residential character and early 20th-century architecture.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Stadionweg Target entity description: Stadionweg is a major street in Amsterdam’s Oud-Zuid district, known for its residential character and early 20th-century architecture.
-
A.
Scheveningseweg
Scheveningseweg is a major historic road in The Hague, Netherlands, connecting the city center with the seaside district of Scheveningen.
-
B.
Bezuidenhoutseweg
Bezuidenhoutseweg is a major street in The Hague, Netherlands, known for its government buildings, offices, and proximity to key city landmarks.
-
C.
Spuistraat
Spuistraat is a central street in Amsterdam known for its historic buildings, shops, and proximity to major city landmarks.
-
D.
Spaklerweg
Spaklerweg is a metro station in Amsterdam that serves as a stop on the city’s rapid transit network.
-
E.
Buiksloterweg
Buiksloterweg is a neighborhood and ferry landing on the northern bank of the IJ in Amsterdam, serving as a key access point between Amsterdam-Noord and the city center.
- 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_69bd445d94788190b72e2cc563120995 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7902fbe48190abb58cb0b2b2b62d |
completed | March 20, 2026, 4:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bed0168a648190a470507802aa8934 |
completed | March 21, 2026, 5:06 p.m. |
| NEDg | Description generation | batch_69bed0b4c8648190a151383277a8297d |
completed | March 21, 2026, 5:09 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69bed14d7a5c8190ac5b09f59a8dda1a |
completed | March 21, 2026, 5:11 p.m. |
Created at: March 20, 2026, 1:44 p.m.