Triple
T29269649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bern agglomeration |
E742074
|
entity |
| Predicate | planningRegionOf |
P55551
|
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: [Bern agglomeration, planningRegionOf, canton of Bern]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: planningRegionOf Context triple: [Bern agglomeration, planningRegionOf, canton of Bern]
-
A.
partOfPlanningRegion
chosen
Indicates that one entity is included within, or belongs to, a larger designated planning region.
-
B.
plannedArea
Indicates that an area is designated or intended for a specific planned use or development.
-
C.
proposedForRegion
Indicates that something has been suggested or designated to apply to, operate in, or be associated with a particular geographic or administrative region.
-
D.
regionTypePlanned
Indicates that a region is intended or designated to have a specific type or classification in a planned or future state.
-
E.
programRegion
Indicates a relationship where a program is associated with, operates in, or is applicable to a specific geographic or administrative region.
- F. None of above.
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_69f0912124d48190a046642b69407f4c |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 28, 2026, 12:47 p.m.