Triple
T33859988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swedish Postcode Lottery |
E867897
|
entity |
| Predicate | hasLotteryFormat |
P49262
|
FINISHED |
| Object | subscription lottery |
—
|
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: subscription lottery | Statement: [Swedish Postcode Lottery, hasLotteryFormat, subscription lottery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLotteryFormat Context triple: [Swedish Postcode Lottery, hasLotteryFormat, subscription lottery]
-
A.
hasTicketFormat
chosen
Indicates that an entity’s ticket is expressed or structured in a particular format.
-
B.
hasRaceFormat
Indicates that an entity is associated with, or characterized by, a particular race format or type of race structure.
-
C.
hasAwardedFormat
Indicates that one entity has granted or assigned a particular award format or type to another entity.
-
D.
hasRaffle
Indicates that an entity organizes, offers, or is associated with a raffle event or activity.
-
E.
hasMatchFormat
Indicates that something (such as a game, event, or competition) is conducted according to a specified match format or structure.
- 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_69f349943ccc8190a3c41a3e0ae46cbf |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69feaa483fcc81909d8a46b38a8717bf |
completed | May 9, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69fea8c9d45c81908ccc8619e5fefac1 |
completed | May 9, 2026, 3:23 a.m. |
Created at: May 1, 2026, 1:47 a.m.