Triple
T28896091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lizardcube |
E732836
|
entity |
| Predicate | gameDeveloperOf |
P35248
|
FINISHED |
| Object | Wonder Boy: The Dragon’s Trap |
—
|
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: Wonder Boy: The Dragon’s Trap | Statement: [Lizardcube, gameDeveloperOf, Wonder Boy: The Dragon’s Trap]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameDeveloperOf Context triple: [Lizardcube, gameDeveloperOf, Wonder Boy: The Dragon’s Trap]
-
A.
gameDeveloper
chosen
Indicates that one entity creates, designs, or develops the other entity, which is a game.
-
B.
gameDeveloperOfAppearance
Indicates that an entity is the developer responsible for creating or producing a particular appearance or version of a game.
-
C.
developerOfContainingGame
Indicates that an entity is the developer responsible for creating the game that contains the referenced element or component.
-
D.
gameDeveloperOfSeries
Indicates that a person or company is the developer responsible for creating or producing one or more games within a particular game series.
-
E.
majorDeveloper
Indicates that an entity is a primary or leading developer responsible for creating or significantly contributing to 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65aa3d0588190bfc2122baa4fb5cd |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f6576487e081908d802f1caf59c423 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 7:59 a.m.