Triple
T36851436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quest for Glory: So You Want to Be a Hero |
E910684
|
entity |
| Predicate | remakeInterface |
P11237
|
FINISHED |
| Object | point-and-click |
—
|
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: point-and-click | Statement: [Quest for Glory: So You Want to Be a Hero, remakeInterface, point-and-click]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: remakeInterface Context triple: [Quest for Glory: So You Want to Be a Hero, remakeInterface, point-and-click]
-
A.
replacedInterface
chosen
Indicates that one interface has been substituted or superseded by another interface.
-
B.
remakePlatform
Indicates that an existing work has been remade or re-released specifically for a different platform or medium.
-
C.
remakeAppearance
Indicates that one entity creates a new version or updated form of another entity’s appearance.
-
D.
remakeLanguage
Indicates that one entity creates a new version or adaptation of another entity in a different language.
-
E.
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).
- 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_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:13 p.m.