Triple

T25533581
Position Surface form Disambiguated ID Type / Status
Subject Steam Workshop E639986 entity
Predicate supportsGameIntegration P143265 FINISHED
Object per-game Workshop hubs 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: per-game Workshop hubs | Statement: [Steam Workshop, supportsGameIntegration, per-game Workshop hubs]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsGameIntegration
Context triple: [Steam Workshop, supportsGameIntegration, per-game Workshop hubs]
  • A. supportsGames
    Indicates that an entity is capable of running, handling, or being compatible with one or more games.
  • B. supportsGameEngine
    Indicates that one entity provides compatibility, functionality, or resources necessary for the operation or integration of a particular game engine.
  • C. supportsGameStreaming
    Indicates that one entity provides the capability for another entity to stream and play games remotely in real time.
  • D. notableGameSupport
    Indicates that an entity is recognized for providing significant support or contribution to a particular game.
  • E. mayBeIntegratedWith chosen
    Indicates that one entity has the potential or capability to be combined or incorporated with another entity into a unified or interoperable whole.
  • 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_69e75dbf3f9c8190b3f2a75d1b75d127 completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f7516d5b4081908588a6feb541f355 completed May 3, 2026, 1:45 p.m.
PD Predicate disambiguation batch_69f74d40ebb081909daf60623e38f41d completed May 3, 2026, 1:27 p.m.
Created at: April 21, 2026, 3:16 p.m.