Triple
T17585913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asynchronous Advantage Actor-Critic |
E428319
|
entity |
| Predicate | outperformsOn |
P42712
|
FINISHED |
| Object | many Atari 2600 games |
—
|
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: many Atari 2600 games | Statement: [Asynchronous Advantage Actor-Critic, outperformsOn, many Atari 2600 games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outperformsOn Context triple: [Asynchronous Advantage Actor-Critic, outperformsOn, many Atari 2600 games]
-
A.
improvesOn
Indicates that one entity enhances, refines, or performs better than another entity, typically by addressing its limitations or increasing its effectiveness.
-
B.
surpasses
chosen
Indicates that one entity exceeds or goes beyond another in degree, quality, performance, or achievement.
-
C.
fasterThan
Indicates that one entity moves, operates, or progresses at a higher speed than another entity.
-
D.
wonForPerformance
Indicates that an entity received an award or recognition specifically for the quality of its performance in some activity or role.
-
E.
isStrongerThan
Indicates that one entity possesses greater physical power, force, or effectiveness than another entity.
- 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_69d889e1030481909950e140c63255b9 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e463d22f908190ae0f1eeafbe54459 |
completed | April 19, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fff0348190b899a32da537eaca |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.