Triple

T1612983
Position Surface form Disambiguated ID Type / Status
Subject Unity E34651 entity
Predicate supportsPlayMode P203 FINISHED
Object in-editor playtesting 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: in-editor playtesting | Statement: [Unity, supportsPlayMode, in-editor playtesting]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsPlayMode
Context triple: [Unity, supportsPlayMode, in-editor playtesting]
  • A. supportsFeature chosen
    Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
  • B. playType
    Indicates the specific category or style of play or performance associated with an event or action.
  • C. supportsAirPlay
    Indicates that one entity is capable of sending or receiving media via Apple’s AirPlay streaming protocol in relation to another entity.
  • D. playsOn
    Indicates that one entity participates or performs on a particular team, platform, or medium.
  • E. supportsAudioQuality
    Indicates that one entity provides or is compatible with a specified level or type of audio quality for another entity or context.
  • 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_69a885ffc5ec819091afa325d5f9611c completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69a93fef600c819080fe75c42c8e6dac completed March 5, 2026, 8:33 a.m.
PD Predicate disambiguation batch_69a907c52a548190b648a31ea306dd5b completed March 5, 2026, 4:34 a.m.
Created at: March 4, 2026, 7:28 p.m.