Triple
T6799086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nordic Council Literature Prize |
E156134
|
entity |
| Predicate | awardAnnouncementLocation |
P3059
|
FINISHED |
| Object | session of the Nordic Council |
—
|
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: session of the Nordic Council | Statement: [Nordic Council Literature Prize, awardAnnouncementLocation, session of the Nordic Council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: awardAnnouncementLocation Context triple: [Nordic Council Literature Prize, awardAnnouncementLocation, session of the Nordic Council]
-
A.
announcementLocation
chosen
Indicates the place or venue where an announcement is made or presented.
-
B.
awardBodyHeadquarters
Indicates the location where the governing or administrative headquarters of the awarding body is situated.
-
C.
locationOfAwardedWork
Indicates the place where the work for which an award was given was created, performed, or took place.
-
D.
awardLocale
Indicates the place or geographic location where an award is given or recognized.
-
E.
announcesAwardsIn
Indicates that an entity publicly declares or presents awards within a particular context, event, or medium.
- 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_69c6881844448190a65822d9b39d7f88 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d2cb6b2881909b30bb8020a9d3bf |
completed | March 27, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69c6d099bf08819089a9f9894d037e74 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:15 p.m.