Triple
T29175591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vossa Jazz |
E739598
|
entity |
| Predicate | hasCommissionSeries |
P83681
|
FINISHED |
| Object | Tingingsverket |
—
|
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: Tingingsverket | Statement: [Vossa Jazz, hasCommissionSeries, Tingingsverket]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommissionSeries Context triple: [Vossa Jazz, hasCommissionSeries, Tingingsverket]
-
A.
tieneComisiones
Indicates that an entity is associated with or subject to commissions, such as fees or percentage-based charges.
-
B.
commissionsAs
Indicates that one entity formally authorizes or hires another entity to create, perform, or carry out a specific work, task, or service.
-
C.
isCommissionSource
Indicates that one entity serves as the origin or basis from which another entity’s commission or referral fee is generated.
-
D.
commissionSeries
chosen
Indicates that an entity (typically a person or organization) initiates and authorizes the creation or production of a series of related works or items.
-
E.
numberOfCommissions
Indicates the quantity of commissions associated with or assigned to 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_69f07cb6394c8190ab7842c48e699e2a |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_6a0049e40d60819081e3899d8d9fca51 |
completed | May 10, 2026, 9:03 a.m. |
| PD | Predicate disambiguation | batch_6a0048c47b548190ad31b2901cc3784a |
completed | May 10, 2026, 8:58 a.m. |
Created at: April 28, 2026, 11:54 a.m.