Triple
T20810290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regensdorf |
E512278
|
entity |
| Predicate | borderedBy |
P224
|
FINISHED |
| Object | Unterengstringen |
—
|
NE NERFINISHED |
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: Unterengstringen | Statement: [Regensdorf, borderedBy, Unterengstringen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Unterengstringen Context triple: [Regensdorf, borderedBy, Unterengstringen]
-
A.
Unterengstringen
chosen
Unterengstringen is a small municipality in the canton of Zurich in northern Switzerland, situated along the Limmat River near the city of Zurich.
-
B.
Unten
Unten is a small coastal settlement on Izena Island in Okinawa Prefecture, Japan.
-
C.
Untergöhren
Untergöhren is a small settlement in the Mecklenburg Lake District of northeastern Germany, situated near Lake Fleesensee and known for its tranquil, lakeside rural setting.
-
D.
Untermetten
Untermetten is a locality or district that forms part of the municipality of Metten in Bavaria, Germany.
-
E.
Dettenschwang
Dettenschwang is a village and district of the market town Dießen am Ammersee in the Bavarian region of Germany.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4cd25088190b48ca9700cd24efc |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2d27a4881908b34679385d8b94b |
completed | April 21, 2026, 12:20 a.m. |
Created at: April 16, 2026, 12:40 p.m.