Triple
T18794604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epic Games |
E459598
|
entity |
| Predicate | platformOffered |
P16033
|
FINISHED |
| Object | PC digital distribution |
—
|
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: PC digital distribution | Statement: [Epic Games, platformOffered, PC digital distribution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: platformOffered Context triple: [Epic Games, platformOffered, PC digital distribution]
-
A.
offeredTechnology
Indicates that one entity has provided or proposed a specific technology to another entity as an option for use, adoption, or consideration.
-
B.
platformShowcased
Indicates that a platform is prominently presented or highlighted, typically to draw attention to its features, capabilities, or offerings.
-
C.
offeredService
chosen
Indicates that one entity has provided or made available a service to another entity.
-
D.
platformStrategy
Indicates a relationship where an entity defines or employs an overarching plan for building, managing, or leveraging a platform to create and capture value among its participants.
-
E.
offersServiceIn
Indicates that a provider makes a particular service available within a specified location or jurisdiction.
- 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5a01dbb308190bbbbd5a18e26451e |
completed | April 20, 2026, 3:40 a.m. |
| PD | Predicate disambiguation | batch_69e48d16dd34819096e096d0c0e4c15c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:53 a.m.