Triple
T17521213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | REINFORCE |
E426681
|
entity |
| Predicate | commonImplementation |
P3697
|
FINISHED |
| Object | neural network policy |
—
|
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: neural network policy | Statement: [REINFORCE, commonImplementation, neural network policy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonImplementation Context triple: [REINFORCE, commonImplementation, neural network policy]
-
A.
commonlyImplementedBy
chosen
Indicates that the referenced item (e.g., a standard, interface, or pattern) is frequently realized or put into practice by the associated implementing entities.
-
B.
exampleImplementation
Indicates that one entity serves as a concrete, illustrative implementation or instance of another, more general concept, design, or specification.
-
C.
commonIn
Indicates that something frequently occurs, appears, or is found within a specified context, group, or environment.
-
D.
commonOn
Indicates that two or more entities share the same location, context, or medium where they are present or occur together.
-
E.
commonFor
Indicates that something is typical, usual, or frequently occurring for a given entity or context.
- 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.