Triple
T29182541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wonder Boy III: The Dragon's Trap |
E739781
|
entity |
| Predicate | remakePublisher |
P166929
|
FINISHED |
| Object | Dotemu |
—
|
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: Dotemu | Statement: [Wonder Boy III: The Dragon's Trap, remakePublisher, Dotemu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: remakePublisher Context triple: [Wonder Boy III: The Dragon's Trap, remakePublisher, Dotemu]
-
A.
relaunchPublisher
Indicates restarting or reactivating a previously halted or inactive publisher’s operations or services.
-
B.
reprintPublisher
Indicates that an entity serves as the publisher responsible for issuing a reprinted edition of a work.
-
C.
remakeDeveloper
Indicates that a developer is responsible for creating a new version or adaptation of an existing work (such as a game, app, or software).
-
D.
remakeDirector
Indicates that the subject is the director of a remake of the object work (e.g., film, show, or other media).
-
E.
formerPublisher
Indicates that one entity previously served as the publisher of another entity but no longer holds that role.
- F. None of above. chosen
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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f664aa283c8190a869d0555eff60c6 |
completed | May 2, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f6645a615481909b53d94512ecbaf1 |
completed | May 2, 2026, 8:53 p.m. |
Created at: April 28, 2026, 11:58 a.m.