Triple
T36955148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xbox and Bethesda Developer Direct January 2023 |
E914170
|
entity |
| Predicate | publisherShown |
P1760
|
FINISHED |
| Object | Xbox Game 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: Xbox Game Studios | Statement: [Xbox and Bethesda Developer Direct January 2023, publisherShown, Xbox Game Studios]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publisherShown Context triple: [Xbox and Bethesda Developer Direct January 2023, publisherShown, Xbox Game Studios]
-
A.
hasPublisher
chosen
Indicates that an entity is published or issued by a specific publisher.
-
B.
publisherProgram
Indicates a program or initiative operated by a publisher that manages or governs its relationships, activities, or offerings with participating entities.
-
C.
publisherStatus
Indicates the current operational or business state of a publisher in relation to the referenced entity or system.
-
D.
publisherType
Indicates the classification or category of a publisher in relation to a published work or entity.
-
E.
publisherPlanned
Indicates that a publisher has scheduled or intends to release or distribute a particular work or item.
- 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_69f76e8b28848190abd81fe7a7374910 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffc704e1e88190884928a6a5c55a87 |
completed | May 9, 2026, 11:45 p.m. |
| PD | Predicate disambiguation | batch_69ffc6b483d881908ad872e25fa6abc5 |
completed | May 9, 2026, 11:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.