Triple
T15074114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golden Hall |
E379953
|
entity |
| Predicate | municipalUse |
P117212
|
FINISHED |
| Object | Stockholm city events |
—
|
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: Stockholm city events | Statement: [Golden Hall, municipalUse, Stockholm city events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: municipalUse Context triple: [Golden Hall, municipalUse, Stockholm city events]
-
A.
municipalScope
Indicates that something falls within the authority, jurisdiction, or functional domain of a municipality or local city government.
-
B.
municipalOwnership
Indicates that an entity is owned, controlled, or held as property by a municipal (city or local) government.
-
C.
usesMunicipalGovernmentAct
Indicates that an entity operates under, applies, or is governed by the provisions of a Municipal Government Act.
-
D.
isMunicipal
Indicates that something belongs to, is administered by, or is characteristic of a municipality or local city government.
-
E.
municipalIntegration
Indicates the incorporation or coordination of local governmental functions, services, or jurisdictions into a unified municipal framework.
- 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_69d85cd7683881908d405c1b5d7b4f7f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69dff7fa0570819088a97b28173154cd |
completed | April 15, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69deb95a182081908fffc4402b02a394 |
completed | April 14, 2026, 10:02 p.m. |
| PDg | Predicate description generation | batch_69dec71e8dcc81908badc834b6ccf273 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:02 a.m.