Triple
T4586065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Double DQN |
E101969
|
entity |
| Predicate | frameworkSupport |
P58147
|
FINISHED |
| Object | implemented in many deep RL libraries |
—
|
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: implemented in many deep RL libraries | Statement: [Double DQN, frameworkSupport, implemented in many deep RL libraries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frameworkSupport Context triple: [Double DQN, frameworkSupport, implemented in many deep RL libraries]
-
A.
frameworkPresented
Indicates that a particular framework has been formally introduced or shown to an audience or recipient.
-
B.
frameworkName
Indicates that a specific framework is identified by the given name.
-
C.
frameworkFor
Indicates that one entity serves as a supporting structure, system, or basis that organizes, guides, or enables the development or functioning of another entity.
-
D.
frameworkEstablishedBy
Indicates that a framework was created, set up, or instituted by a particular agent or entity.
-
E.
appliesFramework
Indicates that one entity uses or implements a particular framework in relation to another entity or context.
- 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_69bd43d4ce208190b53158c882b222e3 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5906a43c81908fb11bf8f94be122 |
completed | March 20, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69bd522acbcc8190bf24d9517793a2c1 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56b4a9508190acdb888eef18f1ee |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:10 p.m.