Triple
T6053726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riehen |
E134855
|
entity |
| Predicate | hasTwinTown |
P919
|
FINISHED |
| Object | Muttenz |
E214435
|
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: Muttenz | Statement: [Riehen, hasTwinTown, Muttenz]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Muttenz Context triple: [Riehen, hasTwinTown, Muttenz]
-
A.
Muttenz
chosen
Muttenz is a municipality in northern Switzerland that serves as a major suburban and industrial center in the canton of Basel-Landschaft, adjacent to the city of Basel.
-
B.
Neuenegg
Neuenegg is a Swiss municipality in the canton of Bern, known for its rural character and location near the city of Bern.
-
C.
Bönigen
Bönigen is a Swiss village in the canton of Bern, known for its scenic location on the shore of Lake Brienz near Interlaken.
-
D.
Selzach
Selzach is a Swiss municipality located in the canton of Solothurn, known for its rural character and proximity to the Jura Mountains.
-
E.
Aarburg
Aarburg is a historic Swiss town in the canton of Aargau, known for its prominent riverside fortress overlooking the Aare River.
- 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_69c00877b6d4819096b0e163728b73a3 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05708fda48190ad3d1860969ebb6a |
completed | March 22, 2026, 8:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6384cf18481909e8cc7f8d35ba2c5 |
completed | March 27, 2026, 7:57 a.m. |
Created at: March 22, 2026, 4:09 p.m.