Triple
T29894042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guldbagge Award for Best Actress in a Leading Role |
E759228
|
entity |
| Predicate | hasAwardedNotableWinner |
P108897
|
FINISHED |
| Object | Liv Ullmann |
—
|
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: Liv Ullmann | Statement: [Guldbagge Award for Best Actress in a Leading Role, hasAwardedNotableWinner, Liv Ullmann]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAwardedNotableWinner Context triple: [Guldbagge Award for Best Actress in a Leading Role, hasAwardedNotableWinner, Liv Ullmann]
-
A.
notableAwardWon
Indicates that an entity has received a specific notable award as a winner.
-
B.
notableAwardedFor
Indicates that an award is notable specifically for being given in recognition of a particular work, achievement, or contribution.
-
C.
notableHolderAwardedTo
chosen
Indicates that a notable award or honor has been conferred upon a particular recipient.
-
D.
notableAwardRecognition
Indicates that an entity has received or been formally recognized with a notable award or honor.
-
E.
notableAwardAdministered
Indicates that an entity is responsible for organizing, managing, or overseeing the administration of a notable award.
- 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_69f2245f1cf88190978c70d1a1d2cb73 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67729a7ac8190b99cf3fcc0e2c60c |
completed | May 2, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:03 p.m.