Triple
T38462999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RPM Racing |
E912496
|
entity |
| Predicate | developerLaterKnownAs |
P158419
|
FINISHED |
| Object | Blizzard Entertainment |
—
|
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: Blizzard Entertainment | Statement: [RPM Racing, developerLaterKnownAs, Blizzard Entertainment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developerLaterKnownAs Context triple: [RPM Racing, developerLaterKnownAs, Blizzard Entertainment]
-
A.
laterDeveloper
Indicates that one developer’s work, role, or involvement occurs after another developer in time.
-
B.
authorLaterBecame
Indicates that the subject, who is an author of something, subsequently took on or transitioned into the role or status specified by the object at a later time.
-
C.
developerRenamedTo
chosen
Indicates that a developer previously known by one name is now identified by a new name.
-
D.
composerLaterKnownFor
Indicates that the person composed the work before becoming widely recognized or primarily known for other, later works.
-
E.
formerDeveloper
Indicates that an entity previously worked as a developer for another entity but no longer holds that role.
- 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_69f76e861d8c81908559031dc66e3c15 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe38be079c8190a240191ac0e73e3a |
completed | May 8, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69fe350344508190930de2218156ca02 |
completed | May 8, 2026, 7:09 p.m. |
Created at: May 3, 2026, 4:31 p.m.