Triple
T7087836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steam |
E165120
|
entity |
| Predicate | Steamworks |
P40486
|
FINISHED |
| Object | game developer tools and services |
—
|
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: game developer tools and services | Statement: [Steam, Steamworks, game developer tools and services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Steamworks Context triple: [Steam, Steamworks, game developer tools and services]
-
A.
studioHost
Indicates that one entity serves as the host or presenter within a studio setting for another entity or program.
-
B.
gameDevelopmentPlatform
chosen
Indicates a platform or environment used for creating, developing, and possibly deploying games.
-
C.
toolUsed
Indicates that an action or task is performed using a particular tool as the means or instrument.
-
D.
studioManager
Indicates that one entity holds managerial responsibility or oversight for a studio associated with another entity.
-
E.
hasDevelopmentStudioIn
Indicates that an entity has a development studio located in a specified place.
- 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_69c6887d98408190912b9580666b0c1d |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e52d26f08190917e5e13b181bdae |
completed | March 27, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c172148190bf290c07bf579d1f |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:41 p.m.