Triple
T14292715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stichtse Vecht |
E354355
|
entity |
| Predicate | containsSettlement |
P847
|
FINISHED |
| Object | Tienhoven |
E1092523
|
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: Tienhoven | Statement: [Stichtse Vecht, containsSettlement, Tienhoven]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tienhoven Context triple: [Stichtse Vecht, containsSettlement, Tienhoven]
-
A.
Tienhoven
chosen
Tienhoven is a small village in the Dutch province of Utrecht, known for its rural landscape and location within the municipality of Stichtse Vecht.
-
B.
Schoonhoven
Schoonhoven is a historic Dutch town in South Holland, renowned for its silver craftsmanship and picturesque riverside setting.
-
C.
Thienhoven
Thienhoven was one of the ships in the early 18th-century Dutch expedition led by explorer Jacob Roggeveen during his voyage across the Pacific.
-
D.
Zwanenburg
Zwanenburg is a village in North Holland, Netherlands, situated near Amsterdam and known as a suburban residential community within the Haarlemmermeer municipality.
-
E.
Veldhoven
Veldhoven is a town and municipality in the southern Netherlands, located near Eindhoven in the province of North Brabant.
- 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_69d8278e17088190b328c5a9d4be74ff |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de7179368081908117a9ccfbf94fd4 |
completed | April 14, 2026, 4:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0bd35543848190992a934d417ac1c4 |
completed | May 19, 2026, 3:04 a.m. |
Created at: April 10, 2026, 1:11 a.m.