Triple
T25307899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Powerball |
E634530
|
entity |
| Predicate | additionalOption |
P30191
|
FINISHED |
| Object | Power Play |
—
|
NE NERFINISHED |
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: Power Play | Statement: [Powerball, additionalOption, Power Play]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: additionalOption Context triple: [Powerball, additionalOption, Power Play]
-
A.
additionalPoints
Indicates that one entity grants or is associated with extra points or bonus scoring in relation to another entity.
-
B.
alternativeFlag
Indicates that something is marked or designated as an alternative option or variant relative to a primary or default choice.
-
C.
additionalVow
Indicates that an entity makes or is associated with an extra or supplementary vow beyond an initial or primary vow.
-
D.
upgradeOption
chosen
Indicates that one entity serves as a possible improved or higher-level alternative to another entity.
-
E.
optionedBy
Indicates that the rights to develop, produce, or exploit something (such as a work, property, or asset) have been contractually secured by a particular party.
- 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_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 1:25 p.m.