Triple
T37456002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loyalist Item Pack |
E930800
|
entity |
| Predicate | publisherOfRelatedGame |
P87866
|
FINISHED |
| Object | Crate Entertainment |
E930797
|
NE 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: Crate Entertainment | Statement: [Loyalist Item Pack, publisherOfRelatedGame, Crate Entertainment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publisherOfRelatedGame Context triple: [Loyalist Item Pack, publisherOfRelatedGame, Crate Entertainment]
-
A.
publisherOfGames
Indicates that an entity acts as the publisher responsible for releasing or distributing one or more games.
-
B.
gamePublisherOfAppearance
Indicates that one entity is the publisher responsible for releasing a particular appearance or edition of a game.
-
C.
gamePublisherOfWork
chosen
Indicates that one entity is the publisher responsible for releasing or distributing a particular game work.
-
D.
competesInGamePublishedBy
Indicates that one entity participates as a competitor in a game that is published by another entity.
-
E.
relatedGame
Indicates that one game has a notable connection or association with another game, such as shared content, themes, or series.
- F. None of above.
Provenance (4 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffebbd9bac8190b3dca4b7252a2278 |
completed | May 10, 2026, 2:21 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40afce40c88190bcbd6aeee55472b3 |
completed | June 28, 2026, 5:23 a.m. |
| PD | Predicate disambiguation | batch_69ffe93120a08190a44bb64d052eda78 |
completed | May 10, 2026, 2:10 a.m. |
Created at: May 3, 2026, 4:17 p.m.