Triple
T36851435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quest for Glory: So You Want to Be a Hero |
E910684
|
entity |
| Predicate | remakeGraphicsStyle |
P118557
|
FINISHED |
| Object | VGA graphics |
—
|
LITERAL 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: VGA graphics | Statement: [Quest for Glory: So You Want to Be a Hero, remakeGraphicsStyle, VGA graphics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: remakeGraphicsStyle Context triple: [Quest for Glory: So You Want to Be a Hero, remakeGraphicsStyle, VGA graphics]
-
A.
remakeAppearance
Indicates that one entity creates a new version or updated form of another entity’s appearance.
-
B.
remixStyle
Indicates that one creative work reinterprets or reworks another using a particular stylistic approach or technique.
-
C.
remakePlatform
Indicates that an existing work has been remade or re-released specifically for a different platform or medium.
-
D.
symbolicStyle
Indicates that one entity employs or is characterized by a particular symbolic or emblematic style defined by the other entity.
-
E.
graphicsUpdate
chosen
Indicates that a change or refresh operation is performed on graphical content or display elements.
- 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_69f76e8033d48190a59274f86f13be48 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:13 p.m.