Triple
T25307874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hot Spot |
E634529
|
entity |
| Predicate | hasGameStyle |
P1609
|
FINISHED |
| Object | rapid, continuous draws |
—
|
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: rapid, continuous draws | Statement: [Hot Spot, hasGameStyle, rapid, continuous draws]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGameStyle Context triple: [Hot Spot, hasGameStyle, rapid, continuous draws]
-
A.
hasGameType
Indicates that an entity (such as a game or match) is associated with a specific category or type of game.
-
B.
hasStyle
chosen
Indicates that an entity possesses, exhibits, or is characterized by a particular style or manner.
-
C.
hasLobbyStyle
Indicates the stylistic design or aesthetic theme that characterizes a lobby space.
-
D.
hasPowerStyle
Indicates that one entity possesses or exhibits a particular style or manner of using power in relation to another entity or context.
-
E.
hasGameSystem
Indicates that an item, product, or context is associated with or supports a particular game system or rules framework.
- 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_69e75a972c6481909bc11710e8d30a6c |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f4939c49a48190b9fdc2555273915e |
completed | May 1, 2026, 11:50 a.m. |
| PD | Predicate disambiguation | batch_69f4806d93dc8190b9dff4c63186faff |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 1:25 p.m.