Triple

T38060896
Position Surface form Disambiguated ID Type / Status
Subject Riley E950336 entity
Predicate controllableByPlayer P191462 FINISHED
Object true 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: true | Statement: [Riley, controllableByPlayer, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: controllableByPlayer
Context triple: [Riley, controllableByPlayer, true]
  • A. isPlayerControlled chosen
    Indicates that an entity is currently being directed or controlled by a human player rather than by the system or AI.
  • B. controlledByInGame
    Indicates that one in-game entity has control or command over another within the context of the game.
  • C. controllingPlayer
    Indicates which player currently has control or authority over a given game element, object, or situation.
  • D. canBeControlledFrom
    Indicates that one entity has the ability or authority to operate, direct, or manage another entity remotely or indirectly.
  • E. isManualPlayable
    Indicates that something can be performed or operated manually by a person, rather than automatically or by a system.
  • 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_69f76f01e63c819093b6012fc974f35a completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69ff5803c02c81908b63067119f5e684 completed May 9, 2026, 3:51 p.m.
PD Predicate disambiguation batch_69ff576d8b308190b49a1e072a0ae661 completed May 9, 2026, 3:49 p.m.
Created at: May 3, 2026, 4:21 p.m.