Triple
T14731243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | canton of Solothurn |
E346078
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Langendorf |
E166452
|
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: Langendorf | Statement: [canton of Solothurn, contains, Langendorf]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Langendorf Context triple: [canton of Solothurn, contains, Langendorf]
-
A.
Langendorf
chosen
Langendorf is a municipality in the canton of Solothurn in northwestern Switzerland.
-
B.
Langendorf
Langendorf is a municipality in the Weißenfels area of Saxony-Anhalt in eastern Germany.
-
C.
Nauendorf
Nauendorf is a village in the German state of Saxony-Anhalt that forms part of the town of Wettin-Löbejün.
-
D.
Schmargendorf
Schmargendorf is a residential locality in southwestern Berlin known for its quiet streets, historic buildings, and proximity to the Grunewald forest.
-
E.
Dennewitz
Dennewitz is a village in Brandenburg, Germany, historically notable as the site of a major 1813 battle during the Napoleonic Wars.
- 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_69d822e5911c8190ba589f957dbd9ba7 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec26311c8819093a81ff0fa43b33b |
completed | April 14, 2026, 10:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff677b7be08190afc2767835836908 |
completed | May 9, 2026, 4:57 p.m. |
Created at: April 10, 2026, 1:29 a.m.