Triple
T4425326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arcade Learning Environment |
E95193
|
entity |
| Predicate | benchmarkLevel |
P23745
|
FINISHED |
| Object | classic control from pixels |
—
|
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: classic control from pixels | Statement: [Arcade Learning Environment, benchmarkLevel, classic control from pixels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: benchmarkLevel Context triple: [Arcade Learning Environment, benchmarkLevel, classic control from pixels]
-
A.
benchmarkStatus
Indicates the current evaluation state or outcome of a benchmark process applied to an entity or system.
-
B.
benchmarkFor
chosen
Indicates that one entity serves as a standard or reference point against which the performance, quality, or characteristics of another entity are measured or evaluated.
-
C.
testingLevel
Indicates the degree or intensity to which something is examined, evaluated, or tested.
-
D.
trainingLevel
Indicates the degree or stage of training or skill development that an entity has attained.
-
E.
assessmentLevel
Indicates the degree, rating, or intensity assigned to an evaluation or judgment of something.
- 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_69b3453c2a0c8190926b574c90766db9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3554e40ec8190982acc0948da2f42 |
completed | March 13, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69b34f5eabe88190a12b244ea71e46d6 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:30 p.m.