Triple
T4470511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DDPG |
E98481
|
entity |
| Predicate | explorationStrategy |
P55275
|
FINISHED |
| Object | noise added to deterministic policy output |
—
|
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: noise added to deterministic policy output | Statement: [DDPG, explorationStrategy, noise added to deterministic policy output]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: explorationStrategy Context triple: [DDPG, explorationStrategy, noise added to deterministic policy output]
-
A.
usesExplorationMethod
chosen
Indicates that one entity employs or applies a particular exploration method as part of its process or behavior.
-
B.
explorationStatus
Indicates the current state or phase of an exploration process or activity between entities.
-
C.
explores
Indicates actively investigating, traveling through, or examining something in order to discover or learn more about it.
-
D.
explorer
Indicates that an entity engages in the activity of exploring or investigating places, ideas, or domains.
-
E.
explored
Indicates that an entity has traveled through, examined, or investigated another entity or area, typically to discover or learn more about it.
- 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_69b3454b4ae481908967426dd37284d6 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b356fb69a0819099f0005779f4fcac |
completed | March 13, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69b3563bf4f8819081726cde3a34460b |
completed | March 13, 2026, 12:11 a.m. |
Created at: March 12, 2026, 11:34 p.m.