Triple
T6993319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proximal Policy Optimization |
E162136
|
entity |
| Predicate | keyHyperparameter |
P5688
|
FINISHED |
| Object | clip range |
—
|
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: clip range | Statement: [Proximal Policy Optimization, keyHyperparameter, clip range]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyHyperparameter Context triple: [Proximal Policy Optimization, keyHyperparameter, clip range]
-
A.
key
Indicates that one entity functions as a key (literal or metaphorical) that unlocks, enables access to, or provides a crucial solution or control over another entity.
-
B.
keyType
Indicates the classification or category of a key in relation to how it is used or defined within a system or context.
-
C.
keyArgument
Indicates that an entity plays a central or primary argumentative role within a larger discourse, claim, or reasoning structure.
-
D.
keyValue
Indicates that one entity functions as a key that is associated with a corresponding value represented by the other entity.
-
E.
keyComponent
chosen
Indicates that one entity is an essential or foundational part required for the proper function, structure, or identity of another entity.
- 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_69c68856d7808190ab33ee914640281b |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dbc30fdc81909244d83c8178755c |
completed | March 27, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c4a18881908d267137daed828b |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:32 p.m.