Triple
T4470488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DDPG |
E98481
|
entity |
| Predicate | valueFunctionType |
P33186
|
FINISHED |
| Object | action-value function |
—
|
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: action-value function | Statement: [DDPG, valueFunctionType, action-value function]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: valueFunctionType Context triple: [DDPG, valueFunctionType, action-value function]
-
A.
variableType
Indicates that one entity is the type or data category of the other entity, which is a variable.
-
B.
value
Indicates that one entity possesses, represents, or corresponds to a particular quantity, quality, or assigned worth.
-
C.
transferFunctionType
Indicates the specific kind or category of transfer function that characterizes how input signals are transformed into output signals in a system.
-
D.
evaluationFunction
chosen
Indicates a relationship where a specific procedure or rule assigns a value or score to an input, typically to assess its quality, utility, or desirability.
-
E.
invocationType
Indicates the manner or mode in which an action, function, or process is called, triggered, or executed.
- 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.