Triple
T4377302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonderbund War |
E99037
|
entity |
| Predicate | belligerent |
P375
|
FINISHED |
| Object | Schwyz |
E282362
|
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: Schwyz | Statement: [Sonderbund War, belligerent, Schwyz]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Schwyz Context triple: [Sonderbund War, belligerent, Schwyz]
-
A.
Schwyz
chosen
Schwyz is a historic canton in central Switzerland, known as one of the founding members that gave the Swiss Confederation its name.
-
B.
Schaffhausen
Schaffhausen is a historic town and capital of the canton of the same name in northern Switzerland, known for its well-preserved medieval old town and proximity to the Rhine Falls.
-
C.
Solothurn
Solothurn is a canton in northwestern Switzerland known for its historic baroque town of the same name and its location along the Aare River.
-
D.
Richterswil
Richterswil is a picturesque municipality on the shores of Lake Zurich in the canton of Zurich, Switzerland.
-
E.
Grenchen
Grenchen is a Swiss town in the canton of Solothurn known for its watchmaking industry and location at the foot of the Jura Mountains.
- 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_69b3454ea8f48190a49c2436624d6ef6 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3523ed220819090cef1a7933489d9 |
completed | March 12, 2026, 11:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bd569f30088190bdc9ea72fe35be35 |
completed | March 20, 2026, 2:15 p.m. |
Created at: March 12, 2026, 11:18 p.m.