Triple
T25588289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hjalmar Gullberg |
E641446
|
entity |
| Predicate | has work in the collection |
P2011
|
FINISHED |
| Object | Svenskt visarkiv |
—
|
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: Svenskt visarkiv | Statement: [Hjalmar Gullberg, has work in the collection, Svenskt visarkiv]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: has work in the collection Context triple: [Hjalmar Gullberg, has work in the collection, Svenskt visarkiv]
-
A.
hasWorkInCollection
chosen
Indicates that a work or item is included as part of a particular collection.
-
B.
hasWorkBy
Indicates that one entity (such as a collection, exhibition, or publication) includes or contains creative works produced by another entity (such as an artist, author, or creator).
-
C.
hasWorkPart
Indicates that one work is a component, section, or constituent part of another, larger work.
-
D.
hasWorkOn
Indicates that one entity is associated with, contributes to, or performs work on another entity (such as a project, task, or artifact).
-
E.
hasWorkCount
Indicates the number of works (such as items, creations, or outputs) associated with a given entity.
- 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_69e75dc42b588190a98b58e0df359674 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f96b32008190ad411ee7472c6b77 |
completed | May 2, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_69f49377411c8190b2188de444d76795 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 4:18 p.m.