Triple
T14157310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Küsnacht |
E350845
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | Heslibach |
E778945
|
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: Heslibach | Statement: [Küsnacht, hasPart, Heslibach]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Heslibach Context triple: [Küsnacht, hasPart, Heslibach]
-
A.
Heslibach
chosen
Heslibach is a locality within the municipality of Küsnacht in the canton of Zürich, Switzerland, known primarily as a residential area along the Lake Zurich shore.
-
B.
Breidenbach
Breidenbach is a small town located in the German region of Westphalia.
-
C.
Weilersbach
Weilersbach is a small municipality in the Forchheim district of Bavaria, Germany, known for its rural character and proximity to the Franconian Switzerland region.
-
D.
Eschbach
Eschbach is a village and district of the town of Usingen in the Hochtaunus region of Hesse, Germany.
-
E.
Urselbach
Urselbach is a small river in the Taunus region of Hesse, Germany, that flows through the town of Oberursel and its surroundings.
- 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_69d8278775fc8190b0802d22ca2f495d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61377de48190a3470d28f0edd34a |
completed | April 14, 2026, 3:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcf7ef4d80819098d210503f5d22e9 |
completed | May 7, 2026, 8:37 p.m. |
Created at: April 10, 2026, 12:58 a.m.