Triple
T8597373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sarphatistraat |
E203584
|
entity |
| Predicate | hasNameInLanguage |
P15
|
FINISHED |
| Object | Sarphatistraat (Dutch) |
E203584
|
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: Sarphatistraat (Dutch) | Statement: [Sarphatistraat, hasNameInLanguage, Sarphatistraat (Dutch)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sarphatistraat (Dutch) Context triple: [Sarphatistraat, hasNameInLanguage, Sarphatistraat (Dutch)]
-
A.
Sarphatistraat
chosen
Sarphatistraat is a major street in Amsterdam known for its long, straight layout and historic 19th-century architecture.
-
B.
Servetstraat
Servetstraat is a small historic street located near Dom Square in the center of Utrecht, Netherlands.
-
C.
Schupstraat
Schupstraat is a prominent street in Antwerp’s Diamond District, known for its dense concentration of diamond shops and related businesses.
-
D.
Leidsestraat
Leidsestraat is a major shopping street in central Amsterdam, known for its many retail stores, restaurants, and tram lines connecting key parts of the city.
-
E.
Reguliersdwarsstraat
Reguliersdwarsstraat is a well-known street in central Amsterdam, noted for its vibrant nightlife, bars, and LGBTQ+ venues.
- 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_69ca832b56948190ba751cec255308f1 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46cacbe88190b95beeedc9f480b0 |
completed | March 31, 2026, 10:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cea8d3fcfc8190bc51a38715ed453e |
completed | April 2, 2026, 5:35 p.m. |
Created at: March 30, 2026, 6:24 p.m.