Triple
T26021516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xbox games |
E647160
|
entity |
| Predicate | publisherIncludes |
P63422
|
FINISHED |
| Object | Microsoft Studios |
—
|
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 Studios | Statement: [Xbox games, publisherIncludes, Microsoft Studios]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publisherIncludes Context triple: [Xbox games, publisherIncludes, Microsoft Studios]
-
A.
includesPublisherFrom
chosen
Indicates that something contains or incorporates a publisher that originates from or is associated with a specified source or context.
-
B.
publisherOfWorkFeaturing
Indicates that one entity serves as the publisher responsible for releasing or distributing a work in which another specified entity is featured.
-
C.
hasPublisher
Indicates that an entity is published or issued by a specific publisher.
-
D.
publishedIn
Indicates that a work (such as an article, paper, or book) has been formally released or made available within a specific venue, medium, or publication.
-
E.
publishedAs
Indicates that an entity is released, issued, or made publicly available under a particular name, format, or identity.
- 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_69e77e8aa65881909ca58918f29ab2a0 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 22, 2026, 9:04 a.m.