Triple
T3525022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Lottery |
E74516
|
entity |
| Predicate | typeOfGambling |
P49260
|
FINISHED |
| Object | legal gambling |
—
|
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: legal gambling | Statement: [National Lottery, typeOfGambling, legal gambling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfGambling Context triple: [National Lottery, typeOfGambling, legal gambling]
-
A.
slot
Indicates a relationship where an entity is assigned or occupies a specific position, time, or opening within an ordered or limited set of available places.
-
B.
betting
Indicates engaging in a wager where one party risks something of value on the outcome of an uncertain event involving another entity.
-
C.
hasCasino
Indicates that an entity includes, contains, or is associated with a casino facility or gambling establishment.
-
D.
gamblerInvolved
Indicates that a gambler participates in, is affected by, or is otherwise directly involved in the specified event or situation.
-
E.
notableGameType
Indicates that a game is of a particular type or category for which the subject is especially well known or notable.
- 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_69ad85d0c5488190a3d8e02ebd01a1aa |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc6a8d0c819094d38b9c47fb67b4 |
completed | March 8, 2026, 6:14 p.m. |
| PD | Predicate disambiguation | batch_69adae121a048190b03825a001d21f49 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb21a437c81908bca88d5e123d744 |
completed | March 8, 2026, 5:30 p.m. |
Created at: March 8, 2026, 3:19 p.m.