Triple
T13543908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soest |
E323462
|
entity |
| Predicate | hasSettlement |
P1068
|
FINISHED |
| Object | Lage Vuursche |
E481214
|
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: Lage Vuursche | Statement: [Soest, hasSettlement, Lage Vuursche]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lage Vuursche Context triple: [Soest, hasSettlement, Lage Vuursche]
-
A.
Lage Vuursche
chosen
Lage Vuursche is a small, historic village in the Dutch province of Utrecht, known for its forests, royal estate nearby, and popular pancake restaurants.
-
B.
Vantongerloo
Vantongerloo is the surname of Georges Vantongerloo, a Belgian abstract artist and sculptor associated with the De Stijl movement.
-
C.
Boesinghe
Boesinghe is a village in West Flanders, Belgium, known for its proximity to key World War I battlefields along the Yser Front.
-
D.
Lage Zwaluwe
Lage Zwaluwe is a village in the Dutch province of North Brabant, known for its proximity to the Biesbosch National Park and its railway connections.
-
E.
Lodewijck
Lodewijck is a Dutch given name, an older or variant spelling of Lodewijk, equivalent to the English name Louis.
- 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_69d8076776248190bdf0d4fa1f85a5fc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafda36248190acabde65a88c5471 |
completed | April 12, 2026, 2:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f75da094288190aff108b006c3da1f |
completed | May 3, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:45 p.m.