Triple
T38604687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LTI Gray Matter |
E934309
|
entity |
| Predicate | publisherForDevelopedGame |
P87866
|
FINISHED |
| Object | Activision |
—
|
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: Activision | Statement: [LTI Gray Matter, publisherForDevelopedGame, Activision]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publisherForDevelopedGame Context triple: [LTI Gray Matter, publisherForDevelopedGame, Activision]
-
A.
publisherOfGames
Indicates that an entity acts as the publisher responsible for releasing or distributing one or more games.
-
B.
gamePublisherOfWork
chosen
Indicates that one entity is the publisher responsible for releasing or distributing a particular game work.
-
C.
gamePublisherOfAppearance
Indicates that one entity is the publisher responsible for releasing a particular appearance or edition of a game.
-
D.
gameProducer
Indicates that one entity is the producer responsible for creating, managing, or overseeing the development of a game associated with another entity.
-
E.
publisherStudio
Indicates that one entity serves as the publishing studio responsible for producing or releasing another entity.
- 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_69f76ecc17688190b389b693a5927501 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a001adc8c108190ab3a43f6415e2be3 |
completed | May 10, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_6a001a290330819097c2c3123f9014b4 |
completed | May 10, 2026, 5:39 a.m. |
Created at: May 3, 2026, 4:32 p.m.