Triple
T37464411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rumble Run |
E930997
|
entity |
| Predicate | supportsReplayability |
P99850
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Rumble Run, supportsReplayability, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsReplayability Context triple: [Rumble Run, supportsReplayability, high]
-
A.
supportsReplayProtection
Indicates that the action or system includes mechanisms to prevent replaying previously valid messages or transactions as if they were new.
-
B.
isReplay
Indicates that an event, action, or content instance is a repeated playback or reproduction of a previously occurring original.
-
C.
hasReplay
Indicates that an event, action, or interaction is available to be viewed or experienced again in a recorded or reconstructed form.
-
D.
usesInstantReplay
Indicates that an entity employs instant replay technology or review during an event, action, or decision process.
-
E.
hasReplayabilityFocus
chosen
Indicates that something is designed or evaluated with an emphasis on being enjoyable or worthwhile to experience multiple times.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.