Triple
T34008894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gambler’s Roll |
E872046
|
entity |
| Predicate | bustEffect |
P178150
|
FINISHED |
| Object | penalty to effect or duration |
—
|
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: penalty to effect or duration | Statement: [Gambler’s Roll, bustEffect, penalty to effect or duration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bustEffect Context triple: [Gambler’s Roll, bustEffect, penalty to effect or duration]
-
A.
breathEffect
Indicates an effect or change that occurs as a direct result of an entity’s breath.
-
B.
ultimateEffect
Indicates the final or overall outcome that results from a preceding action, condition, or sequence of events.
-
C.
eventEffect
Indicates the resulting change, outcome, or consequence that one event has on another state, entity, or event.
-
D.
hasBustOf
Indicates that one entity possesses, displays, or includes a sculpted bust representing another entity.
-
E.
explosionEffect
Indicates that one entity causes or is associated with an explosive event that produces a sudden, forceful effect on its surroundings.
- 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_69f349a08848819084b348d64c1879c3 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70c53062c8190b4cb7be22ab00bc7 |
completed | May 3, 2026, 8:50 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
| PDg | Predicate description generation | batch_69f70b94784c8190970d654e066eb50d |
completed | May 3, 2026, 8:47 a.m. |
Created at: May 1, 2026, 1:51 a.m.