Triple
T38630483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aurora Award |
E937437
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Tromsø International Film Festival award |
C5931
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Tromsø International Film Festival award Context triple: [Aurora Award, instanceOf, Tromsø International Film Festival award]
-
A.
Nordic film award
A Nordic film award is a distinction presented by organizations or festivals in the Nordic countries to recognize outstanding achievements in filmmaking, including direction, acting, writing, and technical crafts.
-
B.
Nordic award
A Nordic award is a formal recognition, typically given by organizations or institutions in the Nordic countries, honoring outstanding achievements or contributions in fields such as culture, science, humanitarian work, or public service.
-
C.
Bodil Award category
A Bodil Award category is a specific division within the Danish Bodil film awards that groups and recognizes achievements in a particular aspect of filmmaking, such as acting, directing, or technical craft.
-
D.
European Film Award category
A European Film Award category is a specific classification within the European Film Awards that groups and recognizes films, filmmakers, or cinematic achievements based on defined criteria such as genre, role, or technical craft.
-
E.
film festival award
chosen
A film festival award is a recognition given at a film festival to honor outstanding achievements in filmmaking, such as directing, acting, writing, or technical craft, among the works presented at the event.
- F. None of above.
Provenance (1 batch)
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_69f76ed5ca3c81909288f61fbf37b359 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:32 p.m.