Triple
T27750424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microsoft Windows games |
E702098
|
entity |
| Predicate | hasRegionalMarket |
P12320
|
FINISHED |
| Object | global |
—
|
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: global | Statement: [Microsoft Windows games, hasRegionalMarket, global]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionalMarket Context triple: [Microsoft Windows games, hasRegionalMarket, global]
-
A.
hasMarketingRegion
Indicates that an entity is associated with or assigned to a specific marketing region for targeting, management, or analysis purposes.
-
B.
marketRegion
chosen
Indicates the geographic or demographic area in which a product, service, or entity is actively marketed or targeted.
-
C.
hasRegionalEntity
Indicates that one entity includes, governs, or is associated with another entity that functions as its regional subdivision or component.
-
D.
isRegional
Indicates that something pertains to, is characteristic of, or is limited to a specific geographic region or area.
-
E.
hasRegionalServices
Indicates that an entity provides or is associated with services that operate within a specific geographic region or set of regions.
- 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_69fefa064ab48190925759950d0d94d9 |
completed | May 9, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_69fef96ae5d08190b027435753c44821 |
completed | May 9, 2026, 9:07 a.m. |
Created at: April 27, 2026, 4:19 p.m.