Triple
T1546951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Frisia |
E32998
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Esens |
E217603
|
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: Esens | Statement: [East Frisia, contains, Esens]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Esens Context triple: [East Frisia, contains, Esens]
-
A.
Sneek
Sneek is a historic Dutch city known for its waterways, sailing culture, and the iconic Waterpoort gate.
-
B.
Maassluis
Maassluis is a historic port town in the province of South Holland in the Netherlands, situated along the Nieuwe Waterweg west of Rotterdam.
-
C.
Vechta
chosen
Vechta is a town in Lower Saxony, Germany, known for its historical significance, university, and annual Stoppelmarkt fair.
-
D.
Alblasserdam
Alblasserdam is a town and municipality in the western Netherlands, situated along the Noord River and known for its proximity to the Kinderdijk windmills.
-
E.
Oranjewoud
Oranjewoud is a historic estate and village in the Dutch province of Friesland, long associated with the royal House of Orange-Nassau.
- 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_69a885ee6db8819099502bc5ce8af881 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abb20dd5a88190b3d6e6f0004fe9b4 |
completed | March 7, 2026, 5:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bfce95558c8190b310e00bd494a81a |
completed | March 22, 2026, 11:12 a.m. |
Created at: March 4, 2026, 7:26 p.m.