Triple
T12771462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spuistraat |
E305255
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Begijnhof |
E232581
|
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: Begijnhof | Statement: [Spuistraat, near, Begijnhof]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Begijnhof Context triple: [Spuistraat, near, Begijnhof]
-
A.
Begijnhof
chosen
Begijnhof is a historic, secluded courtyard in central Amsterdam known for its preserved medieval houses and former beguine community.
-
B.
Janskerkhof
Janskerkhof is a historic square in the center of Utrecht, Netherlands, known for its weekly flower market and proximity to the former St. John's Church.
-
C.
Voorhout
Voorhout is a village in South Holland, Netherlands, that forms part of the municipality of Teylingen.
-
D.
Bullewijk
Bullewijk is a small waterway and urban canal in Amsterdam’s southeastern area, integrated into the city’s network of rivers and canals.
-
E.
Nijverdal
Nijverdal is a town in the Dutch province of Overijssel known as a gateway to the Sallandse Heuvelrug National Park and its surrounding natural landscapes.
- 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_69d7bdf2b43c819098ae5aa68e61ea58 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96df4b36c81909bcc913dd5e535f8 |
completed | April 10, 2026, 9:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7304f62288190aa7788fc6fb04254 |
completed | May 3, 2026, 11:23 a.m. |
Created at: April 9, 2026, 5:28 p.m.