Triple
T9093945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pratteln |
E217965
|
entity |
| Predicate | borderedBy |
P224
|
FINISHED |
| Object | Frenkendorf |
E771530
|
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: Frenkendorf | Statement: [Pratteln, borderedBy, Frenkendorf]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Frenkendorf Context triple: [Pratteln, borderedBy, Frenkendorf]
-
A.
Frenkendorf
chosen
Frenkendorf is a municipality in the canton of Basel-Landschaft in northwestern Switzerland, located near the city of Basel.
-
B.
Plittersdorf
Plittersdorf is a village and district of the town of Rastatt in the state of Baden-Württemberg in southwestern Germany.
-
C.
Rheineck
Rheineck is a municipality in the canton of St. Gallen in northeastern Switzerland, situated near the Rhine River and close to the Austrian border.
-
D.
Pennenfeld
Pennenfeld is a residential subdistrict of the Bonn borough of Bad Godesberg in Germany.
-
E.
Friesdorf
Friesdorf is a residential subdistrict of the Bonn borough Bad Godesberg in western Germany.
- 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_69ca83d8ab5881909d8fddae363b32b1 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc96b347d4819085b33d0e20834f47 |
completed | April 1, 2026, 3:53 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d065c0d77081908fd707af138218fd |
completed | April 4, 2026, 1:13 a.m. |
Created at: March 30, 2026, 7:14 p.m.