Triple
T19414476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bern Old Town |
E485671
|
entity |
| Predicate | primaryBuildingPeriod |
P22153
|
FINISHED |
| Object | 15th to 17th centuries |
—
|
LITERAL 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: 15th to 17th centuries | Statement: [Bern Old Town, primaryBuildingPeriod, 15th to 17th centuries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryBuildingPeriod Context triple: [Bern Old Town, primaryBuildingPeriod, 15th to 17th centuries]
-
A.
hasBuildingPeriod
Indicates that a building or structure is associated with a specific time period during which it was constructed or significantly developed.
-
B.
predecessorBuildingDate
Indicates that one building’s construction date precedes that of another building in a temporal sequence.
-
C.
eraOfMajorConstruction
chosen
Indicates the time period during which the primary or most significant phase of construction for an entity took place.
-
D.
primaryServicePeriod
Indicates the main or most significant span of time during which a service, duty, or activity is performed or in effect.
-
E.
originalBuildingConstructed
Indicates that a particular building was initially constructed in its original form or configuration.
- 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_69d8e8d688f881909c85104a62e09d8a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e62af834fc81908cb176076de10c1c |
completed | April 20, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69e4fd68b1f881908d273de1fee81a75 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:37 p.m.