Triple
T14454016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brügg |
E358406
|
entity |
| Predicate | hasNeighboringMunicipality |
P224
|
FINISHED |
| Object | Orpund |
E1036098
|
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: Orpund | Statement: [Brügg, hasNeighboringMunicipality, Orpund]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Orpund Context triple: [Brügg, hasNeighboringMunicipality, Orpund]
-
A.
Orpund
chosen
Orpund is a municipality in the canton of Bern in Switzerland, situated near the city of Biel/Bienne.
-
B.
Ingemund
Ingemund is a Scandinavian masculine given name of Old Norse origin, historically borne by several notable figures in Sweden and Norway.
-
C.
Halvdan
Halvdan is a masculine given name of Scandinavian origin, historically borne by several notable Norwegian figures.
-
D.
Hrothmund
Hrothmund is a legendary Danish prince from the Old English epic Beowulf, known as one of King Hrothgar’s sons and a member of the Scylding royal line.
-
E.
Svein
Svein is a masculine given name of Old Norse origin, commonly used in Scandinavian countries.
- 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91a8bf088190abf5fd4f646b8c62 |
completed | April 14, 2026, 7:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd6d86dbc0819085fef8fa8b45b373 |
completed | May 8, 2026, 4:58 a.m. |
Created at: April 10, 2026, 1:19 a.m.