Triple
T36549156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Standing Stone Games |
E901210
|
entity |
| Predicate | hasGamePlatform |
P122255
|
FINISHED |
| Object | Microsoft Windows |
—
|
NE NERFINISHED |
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: Microsoft Windows | Statement: [Standing Stone Games, hasGamePlatform, Microsoft Windows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGamePlatform Context triple: [Standing Stone Games, hasGamePlatform, Microsoft Windows]
-
A.
appearsInPlatform
chosen
Indicates that an entity is present, available, or featured within a particular platform or system.
-
B.
hasGameSystem
Indicates that an item, product, or context is associated with or supports a particular game system or rules framework.
-
C.
occursOnPlatform
Indicates that an event, action, or process takes place or is carried out on a specified platform.
-
D.
hasAtGradePlatforms
Indicates that the subject has platforms located at the same level as the surrounding ground or track (i.e., not elevated or underground).
-
E.
gamePlatformCategory
Indicates the classification or type of platform on which a game is available or intended to be played.
- 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_69f76e61217081908b79d610fe67b013 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:11 p.m.