Triple

T15465681
Position Surface form Disambiguated ID Type / Status
Subject Boost Rush E372024 entity
Predicate difficultyCharacteristic P2406 FINISHED
Object fast-paced gameplay 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: fast-paced gameplay | Statement: [Boost Rush, difficultyCharacteristic, fast-paced gameplay]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: difficultyCharacteristic
Context triple: [Boost Rush, difficultyCharacteristic, fast-paced gameplay]
  • A. difficulty chosen
    Indicates the level of challenge, complexity, or effort required to perform an action, solve a problem, or achieve a particular outcome.
  • B. difficultyOption
    Indicates a relationship where a particular option specifies or represents a level of difficulty for something (e.g., a task, question, or activity).
  • C. difficultySource
    Indicates that one entity is the cause, origin, or contributing factor to the difficulty or challenge experienced in relation to another entity or situation.
  • D. difficultyRole
    Indicates the level or type of challenge associated with performing a particular role or function.
  • E. difficultyRelativeTo
    Indicates that one entity’s level of difficulty is being compared to and expressed in relation to another entity’s level of difficulty.
  • 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_69d85cc8bd308190886949510b42e764 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e03f680cec8190836a5ec841dee224 completed April 16, 2026, 1:46 a.m.
PD Predicate disambiguation batch_69ded284bd008190b31c53b4f1cebadd completed April 14, 2026, 11:49 p.m.
Created at: April 10, 2026, 3:33 a.m.