Triple
T19450600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adventure (Atari 2600) |
E486603
|
entity |
| Predicate | EasterEggTrigger |
P135945
|
FINISHED |
| Object | using a gray dot to access a hidden room |
—
|
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: using a gray dot to access a hidden room | Statement: [Adventure (Atari 2600), EasterEggTrigger, using a gray dot to access a hidden room]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: EasterEggTrigger Context triple: [Adventure (Atari 2600), EasterEggTrigger, using a gray dot to access a hidden room]
-
A.
eggNumber
Indicates the specific count or identifier assigned to an individual egg within a set or sequence.
-
B.
eggCare
Indicates that an entity performs actions to tend, protect, or maintain the well-being of eggs.
-
C.
eggType
Indicates the specific category or kind of egg associated with an entity (e.g., its classification or type).
-
D.
entranceGimmick
Indicates a distinctive feature, stunt, or presentation style used when someone or something makes an entrance.
-
E.
eggMimicry
Indicates that one entity’s eggs resemble those of another species closely enough to deceive the other species or its predators.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e5004c23308190a087b7941a90725f |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:38 p.m.