Triple
T29101959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guardian Heroes |
E736658
|
entity |
| Predicate | hasRemasterOrPort |
P71635
|
FINISHED |
| Object | Guardian Heroes (Xbox Live Arcade version) |
—
|
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: Guardian Heroes (Xbox Live Arcade version) | Statement: [Guardian Heroes, hasRemasterOrPort, Guardian Heroes (Xbox Live Arcade version)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRemasterOrPort Context triple: [Guardian Heroes, hasRemasterOrPort, Guardian Heroes (Xbox Live Arcade version)]
-
A.
hasRemastering
chosen
Indicates that one version of a work is a remastered form derived from another version of the same work.
-
B.
hasRemasteredAppearanceIn
Indicates that an entity appears in a remastered version of a work or medium.
-
C.
hasRemixVariant
Indicates that one entity is a remix version or reworked variant of another entity.
-
D.
hasRemakeOrRetroVersion
Indicates that one work has been remade or re-released in a retro-style version of the original.
-
E.
hasRemix
Indicates that one creative work is a remix version derived from or based on another work.
- 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69ffb82be8148190a1c870d467a28c80 |
completed | May 9, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69ffb7bbd550819094052e9a0d0ae320 |
completed | May 9, 2026, 10:39 p.m. |
Created at: April 28, 2026, 11:12 a.m.