Triple
T10864728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nieuwmarkt |
E256497
|
entity |
| Predicate | hasLandmark |
P105
|
FINISHED |
| Object | Waag |
E323136
|
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: Waag | Statement: [Nieuwmarkt, hasLandmark, Waag]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Waag Context triple: [Nieuwmarkt, hasLandmark, Waag]
-
A.
Waag
chosen
Waag is a historic weighing house located on the Grote Markt, notable for its traditional role in trade and its characteristic Dutch architecture.
-
B.
De Dam
De Dam is Amsterdam’s central and historic main square, known for its royal palace, national monument, and role as a major public gathering place.
-
C.
Woudenberg
Woudenberg is a small Dutch municipality and town located in the central Netherlands.
-
D.
De Wolden
De Wolden is a rural municipality in the northeastern Netherlands known for its scenic landscapes, small villages, and agricultural character.
-
E.
Waarder
Waarder is a small village in the Dutch province of South Holland, known for its rural character and traditional polder landscape.
- 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_69d6aa83d1448190a66d93c32394d21f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7516b2f148190adbacd35fc8c2056 |
completed | April 9, 2026, 7:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69dff7d5359c8190b46a6b817938eb67 |
completed | April 15, 2026, 8:40 p.m. |
Created at: April 8, 2026, 9:20 p.m.