Triple
T19450645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yars' Revenge |
E486604
|
entity |
| Predicate | hasEasterEgg |
P134342
|
FINISHED |
| Object | hidden developer initials |
—
|
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: hidden developer initials | Statement: [Yars' Revenge, hasEasterEgg, hidden developer initials]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEasterEgg Context triple: [Yars' Revenge, hasEasterEgg, hidden developer initials]
-
A.
hasCheatCodes
Indicates that a game or system includes special codes or commands that allow users to bypass normal rules or gain advantages.
-
B.
hasSurprise
chosen
Indicates that one entity possesses, causes, or is associated with an unexpected event, reaction, or outcome for another entity.
-
C.
hasEgo
Indicates that an entity possesses or exhibits a sense of self-importance, self-centeredness, or inflated self-regard in relation to others.
-
D.
eggCare
Indicates that an entity performs actions to tend, protect, or maintain the well-being of eggs.
-
E.
eggNumber
Indicates the specific count or identifier assigned to an individual egg within a set or sequence.
- 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6338db7c081908793f23592ebef6b |
completed | April 20, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd6e806081909053f325ba01ab6b |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:38 p.m.