Triple
T27750379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microsoft Windows games |
E702098
|
entity |
| Predicate | developerOfPlatform |
P120027
|
FINISHED |
| Object | Microsoft |
—
|
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 | Statement: [Microsoft Windows games, developerOfPlatform, Microsoft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developerOfPlatform Context triple: [Microsoft Windows games, developerOfPlatform, Microsoft]
-
A.
platformDeveloper
chosen
Indicates that one entity is the developer or creator responsible for building or maintaining the other entity as a platform.
-
B.
developerOfVectorPlatform
Indicates that one entity is the developer or creator responsible for building or maintaining a particular vector platform.
-
C.
platformDeveloped
Indicates that a particular platform has been created, built, or produced by a specified developer or organization.
-
D.
majorDeveloper
Indicates that an entity is a primary or leading developer responsible for creating or significantly contributing to another entity.
-
E.
gameDeveloper
Indicates that one entity creates, designs, or develops the other entity, which is a game.
- 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 27, 2026, 4:19 p.m.