Triple
T32561740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bern |
E832245
|
entity |
| Predicate | oldTownIsUNESCOWorldHeritageSite |
P2499
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Bern, oldTownIsUNESCOWorldHeritageSite, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oldTownIsUNESCOWorldHeritageSite Context triple: [Bern, oldTownIsUNESCOWorldHeritageSite, true]
-
A.
oldTownLocatedOn
Indicates that an old town is situated on or along a particular geographic feature, such as a river, coast, or other landmark.
-
B.
oldTownStatus
Indicates that a place holds the designation or characteristics of being an old or historic town.
-
C.
containsHistoricTown
Indicates that one entity geographically includes or encompasses a town that has recognized historical significance.
-
D.
primaryLocationHistoric
Indicates the historically primary or most significant location associated with an entity, such as where it was originally based, founded, or chiefly active in the past.
-
E.
hasWorldHeritageSite
chosen
Indicates that a location or entity possesses or contains a site designated as a UNESCO World Heritage Site.
- 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_69f34926b9848190ace47d2dd0a0de7c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c6084a348190a1b644c398d91589 |
completed | May 3, 2026, 3:50 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:03 a.m.