Triple
T15240950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EuroMillions |
E364251
|
entity |
| Predicate | hasRollover |
P117709
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [EuroMillions, hasRollover, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRollover Context triple: [EuroMillions, hasRollover, true]
-
A.
rolloverUsedFor
Indicates that one entity’s rollover (such as unused capacity, funds, or benefits carried forward) is applied to or utilized for another entity or purpose.
-
B.
rolloverFrom
Indicates that something is transferred or carried over from a previous state, period, or source into a new one.
-
C.
dataRollover
Indicates that unused data from a previous period is carried over for use in a subsequent period.
-
D.
hasRoudNumber
Indicates that an entity is associated with or assigned a specific round number within a sequence of rounds or stages.
-
E.
hasRound
Indicates that an entity possesses, includes, or is associated with a particular round (e.g., a round of an event, game, or process).
- F. None of above. chosen
Provenance (4 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_69d85a0dde7481908fc64d1e82d5d20d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007db9a148190aadea8d5f8b6b261 |
completed | April 15, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69deca899d5c8190be4a7c71e1683c69 |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2ca6148190967c319728ec3661 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:13 a.m.