Triple
T22757235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leidsestraat |
E562879
|
entity |
| Predicate | terminusB |
P388
|
FINISHED |
| Object | Koningsplein |
—
|
NE NERFINISHED |
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: Koningsplein | Statement: [Leidsestraat, terminusB, Koningsplein]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Koningsplein Context triple: [Leidsestraat, terminusB, Koningsplein]
-
A.
Koningsplein
chosen
Koningsplein is a central square in Amsterdam known for its proximity to major canals, shopping streets, and the historic city center.
-
B.
Koningsplein
Koningsplein is a prominent neoclassical square in central Brussels known for its historic buildings and cultural significance.
-
C.
Luxemburgplein
Luxemburgplein is a prominent square in Brussels, Belgium, located near the European Parliament and known as a hub for political and social gatherings.
-
D.
Merwedeplein
Merwedeplein is a residential square in Amsterdam best known for being the neighborhood where Anne Frank lived before going into hiding.
-
E.
Paleizenplein
Paleizenplein is the prominent public square in central Brussels that fronts the Royal Palace and serves as a key ceremonial and urban landmark in the Belgian capital.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e24551ec7881909a9c924dbea155f6 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17a798ae08190b9810bf241613198 |
completed | April 29, 2026, 3:26 a.m. |
Created at: April 17, 2026, 3:25 p.m.