Triple
T37041223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke Nukem 64 |
E916784
|
entity |
| Predicate | hasCheats |
P98975
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Duke Nukem 64, hasCheats, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCheats Context triple: [Duke Nukem 64, hasCheats, yes]
-
A.
hasCheatCodes
chosen
Indicates that a game or system includes special codes or commands that allow users to bypass normal rules or gain advantages.
-
B.
cheatsOn
Indicates that one entity is being unfaithful or disloyal in a committed relationship by engaging in a romantic or sexual involvement with another entity.
-
C.
hasStealthGameplay
Indicates that the subject involves or supports gameplay mechanics centered around stealth, such as avoiding detection or silently bypassing opponents.
-
D.
hasThiefCharacter
Indicates that an entity includes or features a character whose role or identity is that of a thief.
-
E.
hasEasterEggsFrom
Indicates that something contains or includes hidden features, messages, or surprises that originate from or are created by a specified source.
- 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_69f76e93ec4c8190be81cf87354d9155 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff1a972bf08190860696ffcd887c0f |
completed | May 9, 2026, 11:29 a.m. |
| PD | Predicate disambiguation | batch_69ff184005d88190bf38283ebc499b28 |
completed | May 9, 2026, 11:19 a.m. |
Created at: May 3, 2026, 4:14 p.m.