Triple
T17521178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TD3 |
E426680
|
entity |
| Predicate | policyUpdateRule |
P9550
|
FINISHED |
| Object | deterministic policy gradient theorem |
—
|
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: deterministic policy gradient theorem | Statement: [TD3, policyUpdateRule, deterministic policy gradient theorem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policyUpdateRule Context triple: [TD3, policyUpdateRule, deterministic policy gradient theorem]
-
A.
policyShift
Indicates a change or adjustment in an existing policy, typically reflecting a new direction, priority, or approach.
-
B.
policyTool
Indicates that an entity is a tool, mechanism, or instrument used to design, implement, or enforce a policy.
-
C.
typicalRuleModification
Indicates a change made to a standard or default rule, adjusting how that rule normally applies or operates.
-
D.
policySetBy
Indicates that a particular policy is established, defined, or determined by a specific entity or authority.
-
E.
changePolicy
chosen
Indicates that an entity modifies, replaces, or updates an existing policy governing rules, procedures, or behaviors.
- 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_69d889de677081909b22d2657b1f0292 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e452d2f79881909556894728e255ab |
completed | April 19, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f8b9888190aa8a45e09acf4319 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:49 a.m.