Triple
T5157936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oud-Zuid |
E116359
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | P.C. Hooftstraat |
E236750
|
NE FINISHED |
How this triple was built (2 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: P.C. Hooftstraat | Statement: [Oud-Zuid, contains, P.C. Hooftstraat]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: P.C. Hooftstraat Context triple: [Oud-Zuid, contains, P.C. Hooftstraat]
-
A.
P.C. Hooftstraat
chosen
P.C. Hooftstraat is an upscale shopping street in Amsterdam known for its luxury boutiques and high-end international fashion brands.
-
B.
Lepelstraat
Lepelstraat is a village in the Dutch province of North Brabant that forms part of the municipality of Bergen op Zoom.
-
C.
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.
-
D.
Heemstedestraat
Heemstedestraat is a metro station in Amsterdam that serves as a stop on the city’s rapid transit network.
-
E.
Domstraat
Domstraat is a historic street in the center of Utrecht, Netherlands, connecting key landmarks around the Dom Tower and cathedral.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69bee07283c08190a8fc23d3041275ee |
completed | March 21, 2026, 6:16 p.m. |
Created at: March 20, 2026, 1:44 p.m.