Triple
T35422059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Mario World: Super Mario Advance 2 |
E1023821
|
entity |
| Predicate | hasRemadeVersionOf |
P21944
|
FINISHED |
| Object | Super Mario World |
E79495
|
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: Super Mario World | Statement: [Super Mario World: Super Mario Advance 2, hasRemadeVersionOf, Super Mario World]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRemadeVersionOf Context triple: [Super Mario World: Super Mario Advance 2, hasRemadeVersionOf, Super Mario World]
-
A.
hasRemakeBy
Indicates that an original work has been remade or re-created by a specified agent (such as a person, studio, or organization).
-
B.
hasRemake
chosen
Indicates that one work is a new version or recreation of an earlier existing work.
-
C.
hasRemakeOrRetroVersion
Indicates that one work has been remade or re-released in a retro-style version of the original.
-
D.
remadeFor
Indicates that one work has been recreated or adapted specifically for another context, audience, or medium.
-
E.
appearsInRemakeOf
Indicates that an entity appears in a work that is a remake of another original work.
- 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_69f76df6704081909900c60be10d5849 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39dbb0e9388190a5f7cef4ca7d8d3a |
completed | June 23, 2026, 1:04 a.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.