Triple
T29344833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romont SO |
E744139
|
entity |
| Predicate | neighboringMunicipalityCanton |
P171812
|
FINISHED |
| Object | canton of Bern |
—
|
NE NERFINISHED |
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: canton of Bern | Statement: [Romont SO, neighboringMunicipalityCanton, canton of Bern]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neighboringMunicipalityCanton Context triple: [Romont SO, neighboringMunicipalityCanton, canton of Bern]
-
A.
hasNeighbouringCanton
Indicates that one canton is geographically adjacent to and shares a common border with another canton.
-
B.
neighboringCantonsRepresentedBy
Indicates that the neighboring cantons of a given canton are represented by the specified entity or representative.
-
C.
neighbouringMunicipality
Indicates that one municipality directly borders and is adjacent to another municipality.
-
D.
hasNeighboringFrenchCommune
Indicates that one commune is geographically adjacent to another commune located in France.
-
E.
hasNeighboringCantonAcrossLake
Indicates that one canton is directly across a lake from another canton, with the lake forming their mutual boundary.
- F. None of above. chosen
Provenance (4 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_69f0a79a2d748190bc30abd469298b37 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a28b8ea881908733485374771c51 |
completed | May 3, 2026, 1:19 a.m. |
Created at: April 28, 2026, 2:01 p.m.